From b1ff41766f6d51d12358d6ed6da44974f64fd482 Mon Sep 17 00:00:00 2001 From: Zoffix Znet Date: Sat, 18 Mar 2017 12:24:26 -0400 Subject: [PATCH] Include link to info on good commit content --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2c40ae1d119..ecfdd8e5192 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -62,8 +62,8 @@ very basic guidelines: and loosely follow [perlstyle](http://perldoc.perl.org/perlstyle.html). ## Commit messages -How to write a good **and** useful commit message. Commit messages are where you -tell the what, why and how of your commit to others. +How to write [a good **and** useful commit message](https://chris.beams.io/posts/git-commit/). +Commit messages are where you tell the what, why and how of your commit to others. The subject/title of a commit should 50 or less characters ideally. The absolute maximum is 72. Title's usually will tell what you did. You should almost always