Today we had a situation where the master and develop branches in our repository suddenly had "prevent re-writing of history" and "prevent deleting branches" restrictions put on them.
There are a total of 5 people who have administrator access to the repository, and all of us say we didn't do it.
Is there any log we could consult to see how, when, and by whom this permission change occurred?
It prevents "git push --force" against the designated branch. Another way of saying this: fast-forward pushes only are allowed. And yet another way (sorry, so many ways to describe this!): if 'master' is protected with "Prevent Rewrites" then any push to 'origin/master' must include the current 'origin/master' commit somewhere in its ancestry.
The "prevent rewrite" control only affects pushes. It does not affect merges (via the PR merge button) since the resulting merge commit created by the pull-request merge button will always include current "origin/master" as one of the parent commits.
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