From fd49bd2f2d6b525774dcc558fe88466f85f707c9 Mon Sep 17 00:00:00 2001 From: aparajita Date: Tue, 12 Mar 2013 13:40:18 -0300 Subject: [PATCH] Update CONTRIBUTING.md Updated commit message section. --- CONTRIBUTING.md | 142 ++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 113 insertions(+), 29 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5a04118e8..1bde4969b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,43 +33,127 @@ Some things are difficult to unit test in a way that's worthwhile. For instance The style and format of your commit messages are very important to the health of the project. A good commit message helps not only users reading the release notes, but also your fellow Cappuccino developers as they review `git log` or `git blame` to figure out what you were doing. -This is the preferred format of commit messages for complex changes: +Commit messages should be in the following format: - [New:] + : - [OPTIONAL DESCRIPTION ABOUT WHAT THIS THING DOES.] + -Or for fixes: +