While using the seven rules of a great Git commit message:
- Separate subject from body with a blank line
- Limit the subject line to 50 chareacters
- Capitalize the subject line
- Don't end the subject line with a period
- Use imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
Using the rule #1, #2 and #3, you can add an emoji to indentify what the message is about.
For Example:
π Server Response Documents
Added several document showing the usage of class ServerResponse in the response package
Commit Message Type | Emoji :code: |
---|---|
Initial commit | π :tada: |
Improving structure or formating the code | π¨ :art: |
Improving performance | β‘ :zap: |
Removing code or files | π₯ :fire: |
Bugfixing | π :bug: |
Critical hotfix | π :ambulance: |
Introducing new feature | β¨ :sparkles: |
Adding documentation | π :pencil: |
Metadata / Manifest | π :card_index: |
Deploying stuff | π :rocket: |
Updating UI or style files | π :lipstick: |
Updating tests | β
:white_check_mark: |
Make a test pass | βοΈ :heavy_check_mark: |
Update or add security stuff | π :lock: |
Fixing something on MacOS | π :apple: |
Fixing something on Linux | π§ :penguin: |
Fixing something on Windows | π :checkered_flag: |
Fixing something on iOS | π :green_apple: |
Fixing something on Android | π€ :robot: |
Releasing / Version tag | π :bookmark: |
Testing something | π¨ :rotating_light: |
Removing code warnings | :warning: |
Work in progress [WIP] | π§ :construction: |
Fixing continuous integration (CI) build | π :green_heart: |
Adding a dependency | β :heavy_plus_sign: |
Removing a dependency | β :heavy_minus_sign: |
Downgrading dependencies | β¬οΈ :arrow_down: |
Upgrading dependencies | β¬οΈ :arrow_up: |
Pinning dependencies to specific version | π :pushpin: |
Adding CI build system | π· :construction_worker: |
Analytics or tracking code | π :chart_with_upwards_trend: |
Refactoring code | β»οΈ :recycle: |
Work about Docker | π³ :whale: |
Configuration or properties files | π§ :wrench: |
Internationalization and localization | π :globe_with_meridians: |
Fixing typos | βοΈ :pencil2: |
Code that needs to improve | π© :poop: |
Reverting changes | βͺ :rewind: |
Merging branches | π :twisted_rightwards_arrows: |
Updating compiles lib or packages | π¦ :package: |
Update code due to external API changes | π½ :alien: |
Moving or rename repository | π :truck: |
Adding or updating license | π :page_facing_up: |
Breaking changes | π₯ :boom: |
Adding or updating assets | π± :bento: |
Code review changes | π :ok_hand: |
Improving accessibility | βΏ :wheelchair: |
Documenting source code | π‘ :bulb: |
Writing code drunk (lol) | π» :beers: |
Updating text and literals | π¬ :speech_balloon: |
Performing database related changes | ποΈ :card_file_box: |
Adding logs | π :loud_sound: |
Removing logs or changing log level | π :mute: |
Adding contributor(s) | π₯ :busts_in_silhouette: |
Improving user experience or usability | πΈ :children_crossing: |
Making architectural changes | ποΈ :building_construction: |
Working on responsive design | π± :iphone: |
Mock things | π€‘ :clown_face: |
Adding an easter egg | π₯ :egg: |
Adding or updating a .gitignore file | π :see_no_evil: |
Adding or updating snapshots | πΈ :camera_flash: |
Experimenting new things | βοΈ :alembic: |
Working about Kubernetes | βΈοΈ :wheel_of_dharma: |
Tag a commit | π·οΈ :label: |
For more emojis see Emojipedia
Inspired by Gitmoji