-
Notifications
You must be signed in to change notification settings - Fork 160
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 protects branches that are not listed in rfc-0015 #580
Comments
- surrounding branch patterns with ^...$ should solve #580
Idea is to surround the branch inclusion patterns by ^...$ to get a full branch name match. #581 will test this on https://github.com/cloudfoundry/branchprotection-test. Once merged, I will create test branches similar to the ones listed above which should not be touched anymore. If it works as expected, I adapt the org automation. |
Test #581 succeeded. I created a few test branches on repo branchprotection-test similar to the problematic ones on cf-deployment and the remained unprotected after an org automation run: https://github.com/cloudfoundry/community/actions/runs/4694888643/jobs/8323476572
I will file a PR to adapt the org automation coding to generate branch protection include patterns surrounded by ^...$. |
- surround branch include patterns by ^...$ to avoid matching branches containing 'main' or 'v' - fixes #580 - adapt integration test to changed ARD bots
Branch protection automation protected the following branches for cf-deployment:
It should have protected only the
main
branch from this list. Looks like the branch protection protects all branches that includemain
(the default branch of cf-deployment) orv
(from pattern v[0-9]*).Reason seems to be that the inclusionPattern is checked with regexp.MatchString by the branchprotector tool.
https://github.com/cloudfoundry/community/actions/runs/4677029281/jobs/8284059449
The text was updated successfully, but these errors were encountered: