We have recently started working on Stash and currently evaluating how we can restrict write access on branches in a GIT repositories using Stash. Using the Branch Permission option in Stash, we added only certain users to have write access to the Branch...but surprisingly, even after such a setting, all users are able to push their changes to this branch. Are we missing something here ?
Note: We are having v3.3.1 Stash instance for evaluation.
If you are specifically looking for Branch permission options I'd recommend upgrade to at least Stash 3.10 because there is a significant change towards this in the release. Please see the release notes for more information. I hope that helps.
Thanks for your advise. We did upgrade our stash instance to 3.11.2. Again there, I see that a developer for whom is not on the list of valid users with write access to a branch (in our case master branch) is able to push the changes to this restricted branch. Is there any how, i can check what is happening behind the scene so that I can decipher this issue.
Commits Made After Branch Permissions Were Defined
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