Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Any update? I have same issue. I try to make push and said I have no permission. If I remove permission branch and I push again, it works and it use the user that I had before in exception. This happen when using mvn release:prepare
When the push is working, without the branch restrictions, can you check if the commit is made by the same user id you are trying to exclude? You might have a different user id in the git config?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i set the branch configuration with this:
Optional: Add exemptions for any of the selected restrictions. Adding a user or group as an exemption means that it will not apply to them. This is not required; not adding any exemptions means the restriction will apply to everyone.
put the Atlassian (bamboo build machine) user id in the exclusion list for branch "develop"
I checked Prevent all changes, Prevent changes without a pull request, except by Atlassian userID. When bamboo do a release to staging, the Atlassian should automatically update all pom.xml files to the next development version and push the branch backup.
This will work if i remove the "develop" branch in the branch permission, however, once i put it back, it will failed and complain with this error:
'refs/heads/develop' is read-only.Branch refs/heads/develop can only be modified through pull requests.Check your branch permissions configuration with the project administrator.-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's hard to say without more information. Perhaps you can specify what your branch permission configuration is and what you expect and what actually happens?
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.