1. Commit often and focus on the single topic for commit.
2. Do the commits in branches for particular component or task.
3. Commit in informative manner such as if you are adding something new to your code than use ADD – ‘commit subject’, for update use UPDATE – ‘commit subject’, for delete use DELETE – ‘commit subject’, for fixing something use FIX – ‘commit subject’.
4. Use proper and brief description for each commit.
How to improve the quality of your GitHub commit?
Created
Active
Viewed
54 times
1 reply
Oldest first — sorts top-level replies by their creation dates, with the oldest at the top.
Newest first — sorts top-level replies by their creation dates, with the newest at the top.
Latest activity — sorts top-level replies with recent threaded replies or edits at the top.
Highest score — sorts top-level replies by their total votes (highest first).
Your sorting method preferences will be saved.
Sorted by:
Matt Simerson
Matt Simerson
- 1.1k
- 1
- 11
- 22
Instead of going through the considerable effort of coming up with a system for good commit messages (good means: easy for humans to scan and grok AND also easy for machines to parse), consider adhering to something well established like conventional commits.