Branching Model: Can we send email to the pull request creator instead of to the pull request merger?

We have started using the Stash Branching Model to perform automatic merges. We have a limited number of developers with merge permissions.

Consider the following scenario:

David creates a pull request for feature/X into branch release/2.0. Marge merges the pull request. Stash attempts to merge release/2.0 into develop but encounters a merge conflict. In this case Stash will open a pull request for release/2.0 into develop in Marge's name, and send email to Marge.

Is it possible to have the pull request opened and email set to the original pull request creator (David) instead of the merger (Marge)?

1 answer

0 votes

Hi Dana,

Stash does not support that at the moment; it only considers the user that merged the pull request, assuming that the user that initiated the merge 'owns' any fallout of merging the pull request. But I can see how it would make sense to the email to both the pull request author and the person who performed the merge.

Feel free to open an 'improvement' issue on!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

678 views 5 9
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