Skip to content

[INFRA] Set up default rulesets for default and release branches#134

Open
asf-gitbox-commits wants to merge 1 commit into
masterfrom
infrastructure-ruleset-bot/default-branch-protection
Open

[INFRA] Set up default rulesets for default and release branches#134
asf-gitbox-commits wants to merge 1 commit into
masterfrom
infrastructure-ruleset-bot/default-branch-protection

Conversation

@asf-gitbox-commits
Copy link
Copy Markdown

This Pull Request enables the repository to conform with the "sane default security settings" of the Apache Software Foundation by configuring a default branch ruleset that protects the default branch and any release branches.

Note that ~DEFAULT_BRANCH is a GitHub symbolic link to the current default branch (HEAD) of the repository and does not need changing.
If the managing project does not wish to set up these defaults, please close this Pull Request. Alternatively, the project may merge this Pull Request to apply the changes immediately.

If no action is taken, this Pull Request will be automatically merged by the Apache Infrastructure team on 2026-06-14 (30 days from now).

For any further information, please reach us on Slack or at: users@infra.apache.org

Comment thread .asf.yaml
Comment on lines +40 to +41
bypass_teams:
- root
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

i assume this means the rule does not apply to the role called root?

https://github.com/apache/infrastructure-asfyaml#rulesets

Comment thread .asf.yaml Outdated
Comment on lines +37 to +38
- "release/*"
- "rel/*"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

dont need those two here, i suppose we could edit this commit

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Done. Must keep the set in line if we do move to use release branching, but not sure they'd follow this naming pattern if we did.

@neilcsmith-net neilcsmith-net force-pushed the infrastructure-ruleset-bot/default-branch-protection branch from fbb84dc to 4ae53d1 Compare May 18, 2026 18:05
@neilcsmith-net neilcsmith-net requested a review from mbien May 18, 2026 18:08
@mbien
Copy link
Copy Markdown
Member

mbien commented May 19, 2026

tbh i dont like the bypass since i dont see the point of it to have a role with the ability to nuke all key branches of all repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants