Replies: 1 comment 2 replies
-
@rufuspollock, @demenech, @lucasmbispo, @khalilcodes, @anuveyatsu Would love to hear your opinion on this! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I feel like our current system for describing changes in our codebases doesn't yield very informative commit messages and commit history.
Situation (current system)
This is the structure of commit messages we currently use:
Complications
Where is the "why"? Why this change was even made? Is it a bug fix, a new feature, docs, or CI-related change?
Solution
Use Conventional Commits specification instead, with the following commit message structure:
Beta Was this translation helpful? Give feedback.
All reactions