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)?
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 https://jira.atlassian.com!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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