SHELL

git commit messages

Allowed <type> values: #
feat (new feature for the user, not a new feature for build script)
fix (bug fix for the user, not a fix to a build script)
docs (changes to the documentation)
style (formatting, missing semi colons, etc; no production code change)
refactor (refactoring production code, eg. renaming a variable)
test (adding missing tests, refactoring tests; no production code change)
chore (updating grunt tasks etc; no production code change)

git message

git commit -m "Write your message here"

Git messages

If your message says something like: 
Make heroImage.jpg in index.html responsive, 
then that's a good message. 
You could adopt the convention that some developers use of 
prefixing their commit messages with 
feat for feature, 
fix for a bugfix, 
style for changes to your CSS, 
docs for changes related to documentation, 
refactor for refactored code or 
maint for general maintenance.