Skip to content

Add branch protection rules for SM WG #1233

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pivotal-marcela-campo
Copy link
Member

The SM WG would like to keep their own branch protection rules. Adding them in preparation for enforcement of rules on the 8th.

@beyhan beyhan requested review from a team, rkoster, beyhan, stephanme and ameowlia and removed request for a team July 3, 2025 12:07
Copy link
Member

@stephanme stephanme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

org automation readme mentions that the configuration:

allow_disabled_policies: true  # needed to allow branches w/o branch protection

is needed. All existing branch protection config has this configured (generated and branchprotection.yml).

required_status_checks:
strict: true
contexts:
- "EasyCLA"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the EasyCLA check really needed? I thought the CLA check is enforced by an org setting.
At least it is not configured in the generated branch protection rules.

@beyhan beyhan moved this from Inbox to In Progress in CF Community Jul 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants