Today we added a way for you to restrict access to certain branches in your Git repositories. You can select individual users from your team who are allowed to push to certain branches and everyone else will be restricted. Users with restricted access will still be able to pull that branch and view it’s contents through the web app, but they won’t be able to push or merge remotely or delete it or edit its files directly in Beanstalk.
Restricting write access to branches brings us one step closer towards better code review workflow. It allows leaders of larger teams to find peace of mind knowing that nothing is merged into mission critical branches by mistake or without a proper approval process. It also ensures that some branches can never be deleted.
Branch permissions are available for Git repositories on all Beanstalk accounts. You can set them up on the Permissions page under your repository’s settings. You have to be an admin or account owner in order to access the Permissions page.
We’d love to hear what you think about branch permissions and how you think it will change the way you use Beanstalk. Please let us know in the comments!