Serious question: If the name of the branch already has the ticket number, because you create one branch per ticket, why would "poison" commit message with the same information?
If you are worried that with merge to develop branch and following deletion of branch you lose that information then make sure to include that ticket number in the merge commit message. You will have then focus of commit messages in the branch just only on what's really going on in the code.
Well, I also share the same opinion, however, as we currently use Jira + GitHub, if you add your ticket ID to each of your commit messages you’ll see on Jira the number of commits. As I hate repetitive tasks I decided to come up with this ✌️
Serious question: If the name of the branch already has the ticket number, because you create one branch per ticket, why would "poison" commit message with the same information?
If you are worried that with merge to develop branch and following deletion of branch you lose that information then make sure to include that ticket number in the merge commit message. You will have then focus of commit messages in the branch just only on what's really going on in the code.
Hey Richard,
Well, I also share the same opinion, however, as we currently use Jira + GitHub, if you add your ticket ID to each of your commit messages you’ll see on Jira the number of commits. As I hate repetitive tasks I decided to come up with this ✌️
What value can you see by the number of commits?
Actually, I’m not sure 🤔 I reckon that management use them for performance analytics or so
Hi Rafael,
oh, I see... So you are not using JIRA+BitBucket on premise... Carry on... :)