π¦ A list
of common git
commit messages for clear
and consistent
version control. Just copy
, paste
and customize
.
π‘ Inspiration
1.
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.
πͺͺ A standardized
structure used during commits
to maintain clarity
and consistency
in project history.
<emoji> <type>(<scope>): <subject>
<body>
<footer>
π₯ 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>
π 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
π‘ 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
βοΈβπ₯ Feel free
to submit pull requests
to add more commit types
or scope types
to this list.