I'd like to be able to set branch permissions for my Bitbucket repos. I want to restrict access to certain branches for some team members.
Is this possible?
Greetings!
Although we do not support granular permissions on branches, a previously suggested approach would be to fork the repository, providing the Release Manager access to the fork.
The fork can inherit or have its own permissions. As part of the release, you could ask the manager to pull incoming changes from the parent.
This information can be found here if interested:
https://confluence.atlassian.com/display/BITBUCKET/Branching+a+Repository
I hope this response was helpful.
Cheers,
Jason | Atlassian
This is no longer the case. We now have branch permissions! https://confluence.atlassian.com/display/BITBUCKET/Branch+management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We're tracking adding Branch permissions on this issue. Please feel free to comment on the request!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The lack of "push" write access control per branch, or at least to a single ("master") branch, is causing is a lot of trouble. What are the odds of this appearing? We're trying to decide whether to endure for a while (and manually push -f back a bad commit in master every few days), or look elsewhere.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.