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
You can define branch restrictions at Project level, but not at Workspace level, and they are inherited by the repositories. Branch restrictions support merge checks/blocking and direct commits in dev.
I'm not sure what you mean by PR activation, but you can define PR permissions in branch restrictions as well.
Default merge strategy e.g. squash commit is also supported at Project level for the repositories to inherit it. However you can't enforce it or restrict it.
Flowie, a Bitbucket addon we develop, provides more granular control over these and other settings. e.g. It can enforce a merge strategy per branch for all repositories, defined at Workspace level. Additionally, you could also define that it should always close the branch after a merge for instance.