Branch Protection Pattern Bug? #69418
Replies: 1 comment
-
Nvm, I figured this out. The forward slash must be included in the pattern |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
I am unsure if the following is a bug, or is because GitHub for some reason does not support forward slashes in branch names typically used in Gitflow? Notice the branch pattern matches no branches, when clearly there are 4 feature branches. Do I need to change our branch naming pattern, and if so is there documentation on characters in branch names that cause problems in GitHub?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions