My organization has different groups that contribute to our source repository, and they have two different sets of needs for their pull requests. For one group, I'd like to a merge check that requires a successful build and gives a default set of reviewers. For the other group, they won't require a build and they'll enter their own reviewers. I know for setting the default reviewers I could just have the different groups use different branch names that I could recognize as a pattern. But for the successful build, I don't see a way to make the distinction.
Any help would be appreciated
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