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.
Vijay,
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.
https://confluence.atlassian.com/stash/stash-3-10-release-notes-749314613.html
Branch Permissions.
Branch-Permissions.jpg
Commits Made After Branch Permissions Were Defined
Commits-Made-After-Branch-Permissions-Where-Changed.jpg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Attaching the screenshot of branch permission setting as well as the commits that were made after this setting was made.
CommitsMadeAfterPermisisonsWereSet.jpgBranchPermission.jpg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't read those
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.
That looks like it should work. Not sure why it isn't; sorry...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vijay,
As Tim Crall asked, could you please share a screenshot of your branch settings screen?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That seems very odd. Maybe include a screenshot of your branch settings screen? If you've set them up correctly, then people not on the list should not be able to push to that branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.