5 things to keep in mind to write better Git/Github commit messages.
1. Start with a verb (Add, Fix, Update) to indicate what the commit does.
✅
2. Commit message should always be in the present tense to describe what the code does when applied.
❌
✅
3. Your commit message should describe what the commit does and why it is necessary.
❌
✅
4. If applicable, refer to tickets or issues in your commit message.
✅
5. Avoid using complicated technical terms in your commit message to make it understandable across the team.
❌
✅
#git #github #commit
➖➖➖➖➖➖➖➖➖➖➖➖➖
Join @coderblast for more ☑️
Share with your buddies 🤝
1. Start with a verb (Add, Fix, Update) to indicate what the commit does.
✅
Add 2FA for user authentication2. Commit message should always be in the present tense to describe what the code does when applied.
❌
Added, Updated, Fixed, Refactored✅
Add, Update, Fix, Refactor3. Your commit message should describe what the commit does and why it is necessary.
❌
Update styles✅
Update styles for the homepage4. If applicable, refer to tickets or issues in your commit message.
✅
Fixes #14: Resolve issue with form submission5. Avoid using complicated technical terms in your commit message to make it understandable across the team.
❌
Optimize CRUD operations with RESTful APIs using GraphQL✅
Improve data handling for better API performance#git #github #commit
➖➖➖➖➖➖➖➖➖➖➖➖➖
Join @coderblast for more ☑️
Share with your buddies 🤝