I've tried turning on "Require issue keys in commit messages" for some of our repositories - we've always had a general agreement to use issue keys, and I thought enforcing them was a good idea. It's great except for one thing: branch merges. I'm using Mercurial, and we use feature branching, so there's a fair bit of branch / merge effort.
Traditionally, we've merged back to a build branch with a commit message of "Merge", because we may have many stories that need to be completed before the merge takes place.
Is there any way to allow a Merge commit w/o issue keys? I've noticed that you can merge branches in the bitbucket website w/o the key, so there's clearly some way of pulling it off, but I don't want to require using the website to do all our merges, either.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...
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