-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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 Protection Impossible For New Repositories #15705
Labels
type/enhancement
An improvement of existing functionality
Milestone
Comments
Will also be fixed by #20825 |
lunny
added a commit
that referenced
this issue
Jan 16, 2023
This PR introduce glob match for protected branch name. The separator is `/` and you can use `*` matching non-separator chars and use `**` across separator. It also supports input an exist or non-exist branch name as matching condition and branch name condition has high priority than glob rule. Should fix #2529 and #15705 screenshots <img width="1160" alt="image" src="https://user-images.githubusercontent.com/81045/205651179-ebb5492a-4ade-4bb4-a13c-965e8c927063.png"> Co-authored-by: zeripath <art27@cantab.net>
Fixed by #20825 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
If I create a new repository, it is initially empty. In this case, I cannot set up branch protection, at least not via the UI.
Maybe templating could work around this?
...
Screenshots
The text was updated successfully, but these errors were encountered: