Handling merge commits requiring issue keys

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.

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,755 views 1 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you