Browse code
Add notes about git commit messages
This improves readability of commits a lot and is easy to
follow. I think most people follow those rules already. They are based
on http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
Docker-DCO-1.1-Signed-off-by: Johannes 'fish' Ziemke <github@freigeist.org> (github: discordianfish)
Johannes 'fish' Ziemke authored on 2014/05/01 02:23:51Showing 1 changed files
| ... | ... |
@@ -90,6 +90,10 @@ reference to all the issues that they address. |
| 90 | 90 |
|
| 91 | 91 |
Pull requests must not contain commits from other users or branches. |
| 92 | 92 |
|
| 93 |
+Commit messages must start with a capitalized and short summary (max. 50 |
|
| 94 |
+chars) written in the imperative, followed by an optional, more detailed |
|
| 95 |
+explanatory text which is separated from the summary by an empty line. |
|
| 96 |
+ |
|
| 93 | 97 |
Code review comments may be added to your pull request. Discuss, then make the |
| 94 | 98 |
suggested modifications and push additional commits to your feature branch. Be |
| 95 | 99 |
sure to post a comment after pushing. The new commits will show up in the pull |