Git commit accepts several message flags (-m) to allow multiline commits

Re:Git commit accepts several message flags (-m) to allow mu... by bluesign on Wednesday July 08, 2020 @05:04AM (#23768185)

It all depends on how well you use git I guess. Imagine you developed a feature on a branch, then merged it into main. Later you have to change something at that feature, from the commit message you can find the commit, then you can see which parts of code is effected by that.

Then you are working on a subset of code, and can see of your change is effecting something else, or where else you need to make changes.

Or maybe someone fixed a bug there, then from commit message you can go to related bug, see their intentions more clearly.

[ Parent | on HN ]

Re:Git commit accepts several message flags (-m) to allow mu... by sonthonax on Wednesday July 08, 2020 @05:08AM (#23768206)

I’d like to add, squashing is important in this workflow.

A string of commit messages on a branch saying, “add x”, “typo”, say a lot less than a single commit along the lines of “TICKET-XXX new feature”.

[ Parent | on HN ]