- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally
- Consider starting the commit message with an applicable emoji:
- π¨
:art:
when improving the format/structure of the code - π‘
:bulb:
when working on a new idea - π§
:construction:
when working on something highly unfinished - π
:racehorse:
when improving performance - π±
:non-potable_water:
when plugging memory leaks - βοΈ
:pencil2:
when writing docs - π§
:penguin:
when fixing something on Linux - π
:apple:
when fixing something on Mac OS - π
:checkered_flag:
when fixing something on Windows - π
:bug:
when fixing a bug - π₯
:fire:
when removing code or files - π when adding logging
- π when reducing logging
- π
:green_heart:
when fixing the CI build - β
:white_check_mark:
when adding tests - π
:lock:
when dealing with security - β
:heavy_plus_sign:
when adding feature - β
:heavy_minus_sign:
when removing feature - β¬οΈ
:arrow_up:
when upgrading dependencies - β¬οΈ
:arrow_down:
when downgrading dependencies - π
:shirt:
when removing linter warnings - πΏ
:shower:
when cleaning files of comments, adding to gitignore, etc.
- π¨
Last active
January 26, 2016 15:10
-
-
Save MadcapJake/04a32b4e903a1ae0774e to your computer and use it in GitHub Desktop.
Git Commit Message Guidelines
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment