What is the best practice for branching / commit messages when using JIRA issues with subtasks. I typically create a user story and break that story down into technical tasks. However, I was curious how commit messages / feature branching should work so the source tab links up correctly.
Currently I do a bunch of work which results in multiple commits in a feature branch. Once the feature is complete I squash the commits and ensure the commit message references the user story.
Just looking for some best practices...
I think you might be referring to the explanation we give on the JIRA integration document. Basically:
- Any JIRA issue key you mention on your commit messages will be automatically linked in Stash to your JIRA. Stash recognizes a defaul JIRA issue key style as described on the Using custom JIRA issue keys with Stash document.
- The counterpart is that the issue keys on JIRA will pick up all the commits in Stash associated with that JIRA issue key (in your case, there will be an issue key for each story you create).
Does it make sense to you now? I believe the best practice on how to create those issues will be more to you. Stash/JIRA integration will do the rest of the trick to organise the commits/JIRA issue keys for you.
Atlassian Support - DevTools
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs