AzureDevOps all repository policy side effect
Dec 14, 2022
Recently I have decided to stop setting up each repository by hand and make a global police. One policy was applied to “protect the default branch of each repository”. After applying this policy, we couldn’t add any new Wiki pages with the message “Pushes to this branch is not permitted. Please continue with ‘Edit in Repos’ and use a pull request to update this branch. Click on ‘Learn More’ to find out how to edit in Repos.”. There is simple work around — not applying a default branch policy but rather to use one that targets main, master or whatever default name you use.
References:
