##The seven rules of a great git commit message
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
##Other general advce:
- Don't vary wildly in length and form
- teams should first agree on a commit message convention that defines style(syntax, grammar, punctuation), content, metadata(issue tracking IDs, pull request numbers)
##Examples - Good commit messages:
[Make configuration of acceptors and selectors compatible with Jetty 8](https://github.com/spring-projects/spring-boot/commit/69499bf329a5adc17e16dcff8f380e1561767ae2)
Support max-http-header-size & max-http-post-size - https://github.com/spring-projects/spring-boot/commit/6d2f88ed9ba196ed04ecfcc0cc10cbcb267f155f
Add tests for ImportSelector meta-data
Update docbook dependency and generate epub
Fix failing CompositePropertySourceTest
Rework @PropertySource early parsing logic