Commit messages: Difference between revisions
From YM2149.org
Jump to navigationJump to search
(Created page with "Frequently used commit messages for work in progress commits, before squashing into a smaller number of commits for pull request and merge. * undup * port to new api * refactor * refactoring * conciser * experimentally Category:Programming") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== WIP messages == | |||
Frequently used commit messages for work in progress commits, before squashing into a smaller number of commits for pull request and merge. | Frequently used commit messages for work in progress commits, before squashing into a smaller number of commits for pull request and merge. | ||
| Line 7: | Line 9: | ||
* conciser | * conciser | ||
* experimentally | * experimentally | ||
See https://github.com/combatopera/Leytonium/blob/trunk/leytonium/git_completion.bash for a more exhaustive list. | |||
== Conventional commits == | |||
* chores are for computers, not humans | |||
** in the industry there seems to be an ugly trend away from automation of mindless repetitive tasks, or a normalisation of doing them manually | |||
** smells like a trust issue originating with certain individuals who feel insecure unless pulling knobs and levers themselves | |||
** exacerbated by low performers content with jumping through hoops as automation requires skill | |||
* put whatever you like, with a jira reference | |||
** ideally focus on what is being achieved from a user pov | |||
[[Category:Programming]] | [[Category:Programming]] | ||
Latest revision as of 21:01, 23 February 2025
WIP messages
Frequently used commit messages for work in progress commits, before squashing into a smaller number of commits for pull request and merge.
- undup
- port to new api
- refactor
- refactoring
- conciser
- experimentally
See https://github.com/combatopera/Leytonium/blob/trunk/leytonium/git_completion.bash for a more exhaustive list.
Conventional commits
- chores are for computers, not humans
- in the industry there seems to be an ugly trend away from automation of mindless repetitive tasks, or a normalisation of doing them manually
- smells like a trust issue originating with certain individuals who feel insecure unless pulling knobs and levers themselves
- exacerbated by low performers content with jumping through hoops as automation requires skill
- put whatever you like, with a jira reference
- ideally focus on what is being achieved from a user pov
