We are working in a scenario with multiple Projects (with different project Keys) where developers from other Projects will have to make changes in a repo of another Project.
Because of safety critical SW we want to make sure nothing is merged to develop by "externals" without being noticed. The goal would be to allow all Project developers to work as usual (PR to develop, no Default Reviewer). Developers from external Projects on the other hand should not have the possibility to merge to develop without an approval of a default reviewer who is member of the project.
This is why when setting up the branch permissions and default reviewers I am looking for an option to negate the branch expression. -> All branches that do not contain the "allowed" Project key will have default refiewers.
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