Skip to content

⚑ A list of common git commit messages for πŸ’Ž clear and πŸͺ™ consistent version control.

Notifications You must be signed in to change notification settings

divyanshudhruv/gitlog

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

3 Commits
Β 
Β 

Repository files navigation

⚑ Gitlog

πŸ”¦ A list of common git commit messages for clear and consistent version control. Just copy, paste and customize.

πŸ’‘ Inspiration1.


Important

🍰 Before getting started, please familiarize yourself with the proper commit message format, including the use of emojis for different commit types.

Caution

πŸ™ Kindly do not use the default Update file message.


Message format

πŸͺͺ A standardized structure used during commits to maintain clarity and consistency in project history.

<emoji> <type>(<scope>): <subject>

<body>

<footer>

Merge format

πŸ₯ A format used during merges to clearly document merge actions in the project history.

<emoji> <type>(<scope>): <subject>

- <points>
- <points>

Contributor: <user>
Co-contributor: <user>
Closes #<issue>

Commit messages:

πŸŒƒ Common types of commit messages with their corresponding emojis:


0. Initialization

πŸŽ‰ init(): Initial commit

1. Features and enhancement

✨ feat(): New feature
⚑ perf(): Performance improvements
🎨 design(): UI/UX design improvements
πŸ“ˆ analytics(): Analytics or tracking code
πŸ”Œ integration(): External integrations

2. Bug fixes

πŸ› fix(): Bug fix
πŸ” debug(): Debugging changes
πŸ‘¨β€πŸ”§ patch(): Minor fix or patch

3. Documentation

πŸ“š docs(): Documentation changes
πŸ“ update(): Minor updates
πŸ“– guide(): Update or add a guide

4. Code styling and refactoring

πŸ’„ style(): Code formatting
♻️ refactor(): Code refactoring
🧹 cleanup(): Clean-up or refactor of unused code
πŸ› οΈ fix(): Code improvements
πŸ”₯ remove(): Removing files or code

5. Testing and maintenance

βœ… test(): Adding/modifying tests
πŸ”§ chore(): Maintenance tasks
πŸ”¨ build(): Changes to the build process
🚧 wip(): Work in progress
πŸ“Š metrics(): Metrics and monitoring

6. Security and reverting changes

πŸ”’ security(): Security improvements
πŸ“Œ revert(): Reverting previous changes
πŸ›‘οΈ protect(): Security patches or fixes
πŸ”Œ api(): API-related changes

7. Deployments and builds

πŸš€ deploy(): Deploy-related changes
πŸ“¦ build(): Changes to build configuration
πŸ§ͺ ci(): Continuous Integration changes
πŸ”¨ setup(): Setup or config changes

8. Database and infrastructure

πŸ—ƒοΈ db(): Database changes
πŸ‘· infra(): Infrastructure improvements
πŸ“‘ network(): Network configurations or updates

9. Others

πŸ“€ release(): New releases or version bumps
πŸ“œ dumpversion(): Dumping version info or changelog
πŸ”„ ref(): Reference updates or reorganization
πŸ’¬ discussion(): Ongoing discussions or issue resolutions
βš™οΈ config(): Configuration changes
πŸ”§ tweak(): Minor adjustments or tweaks
🚨 alert(): Important notices or warnings

10. Please

πŸ™ pls(): Request or polite suggestion

Commit message scopes:

πŸ’‘ Following scopes are commonly used in commit messages to indicate specific areas of the project affected by the changes:


  • auth
  • api
  • ui
  • database
  • components
  • config
  • tests
  • security
  • build
  • server
  • styles
  • checkout
  • payments
  • notifications
  • user
  • css
  • layout
  • frontend
  • backend
  • forms
  • router

Contributing

⛓️‍πŸ’₯ Feel free to submit pull requests to add more commit types or scope types to this list.


Footnotes

  1. commit-messages ↩

About

⚑ A list of common git commit messages for πŸ’Ž clear and πŸͺ™ consistent version control.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published