It seems to be prevented by default for clear reasons, but we require this for what I believe to be a common scenario:
Enabling a workflow described above requires two things from Stash:
The "downside" would be that the author of a PR would always need to approve the branch, despite the branch containing commits from a single author. This is really just a minor annoyance, though, as it solves a much bigger problem.
There is no way to set the author to be one of the reviewers. If you really want to achieve what you described, the only way to do it is to have a third user create the PR (and probably unwatch it immediately) and set the two authors to be the reviewers.
That said, I do not agree with you on your third point. If two people collaborate on a feature, it really should be reviewed by a third person who did not write any of the code and comes with a fresh pair of eyes.
And we are still only talking about the person who created the PR, *not* the person/people who authored the code. The current restriction is merely a "suggestion" and doesn't enforce anything. It just makes life harder for other workflows. Hence the restriction should be optional. A nice additional option would be to prevent commit authors from approving the PR.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot