News for hackers. Stuff that matters.

A comment on Using Git commit message templates to write better commit messages. Parent comment

Re:Using Git commit message templates to write better commit... by tekno45 on Wednesday January 12, 2022 @06:48PM (#29914532)
isn't the problem described in the jira ticket?
[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by throw0101a on Wednesday January 12, 2022 @08:02PM (#29915377)
> isn't the problem described in the jira ticket?

Yes/perhaps/maybe, but it's nice to (a) have it in front of you without having to change programs or context, and/or (b) have it summarized, as the ticket may have 'extraneous' stuff like a bunch of back-and-forth with the user/client/tester/etc.

[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by erik_seaberg on Wednesday January 12, 2022 @08:40PM (#29915747)
Organizations ought to preserve tickets across migrations to new systems, but they don’t always. Only commits are forever.
[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by icedchai on Thursday January 13, 2022 @07:13AM (#29919898)
Except tons of orgs squash before merge (unfortunately, IMHO) so individual commits are pretty transitory. Doing “conventional commits” for all those smaller commits seems wasteful.
[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by terinjokes on Wednesday January 12, 2022 @10:45PM (#29916605)
They often believe they'll never change ticket systems. Until they find out one morning IT didn't subscribe to the same ideology.
[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by luxurytent on Wednesday January 12, 2022 @08:40PM (#29915739)
Nice to have the problem in line because I can search git history. Also no guarantees that the Jira ticket will be around as long as the code.
[ Parent | on HN ]
Re:Using Git commit message templates to write better commit... by Liquid_Fire on Thursday January 13, 2022 @04:55AM (#29918880)
The problem the commit is addressing might not be exactly the same as the problem in the JIRA ticket (e.g. you're solving a bigger problem than just what the JIRA describes, or there are multiple causes and this commit fixes only one of them, etc).
[ Parent | on HN ]