You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My team create repo for new little applications, but the creator sometime forget to add default reviewer in pull request section of repo.
So, my colleagues may forget to add reviewer in pull request.
Is there a setting to hint/stop this situation? Either default reviewer of team/workspace or flag to disable create PR without reviewer are good.
That's a very common scenario that even for small repositories and teams it makes a lot of sense to have a standardised pull request process, including default reviewers and enforcing approvals before the PR can be merged.
We have built an app - Workzone for Bitbucket cloud (free for up to 5 users) - exactly for that. For your use-case you could define default reviewers at workspace or project level, so new repositories would inherit the reviewer configuration. You can also control when a PR is ready to merge by requiring at least 1 or 2 reviewer approvals, and have Workzone auto-merge the pull request, when all conditions are met.
Let us know if you'd like to touch base on how we can help.
Update: I just checked core Bitbucket.org features. You can set default reviewers on project level, however these reviewers are not branch-specific or file/path specific (with Workzone). Hope that helps.
Unfortunatelly there is no such option. When creating a repo, the creator should think through all aspects, including adding the default reviewer.
That being said, there is an option to notify ther merger of the PR's when no approval has been given by a Default reviewer. So this should then be the trigger to add a Default Reviewer if forgotten.
Disclaimer: Actually blocking the merge requires Bitbucket premium
Got to Branch restrictions (on repo level):
Then click Add a branch restriction and there you will see the option I am talking about:
Hope this helps!