-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Branch policy issue #571
Comments
@decyjphr do we need to have .github/settings.yml all the time ? can we just enforce policies with .github/repos/*.yml |
The settings file is a general file that would apply this protection to all the organization's repositories. If there are repositories that do not have that branch name, you have to reset it to empty in the specific repo file (I don't know if it would also work in the suborg file) and add a new element with the protection configuration of that branch to that specific repository. This will cause the general branch to be deleted from the configuration and only the branch of that repository to be added. This is because by default what the configuration does is add all the configurations that exist. I remember a similar question and it was explained how to do it. I don't know if it is already in the documentation or it was left as a comment in some issue. |
branch policies have issue if you .github/settings doesn't have the same branch as repo.yml
The text was updated successfully, but these errors were encountered: