Skip to content

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

Merged
JingsongLi merged 1 commit into
masterfrom
infrastructure-ruleset-bot/default-branch-protection
May 24, 2026
Merged

[INFRA] Set up default rulesets for default and release branches#7872
JingsongLi merged 1 commit into
masterfrom
infrastructure-ruleset-bot/default-branch-protection

Conversation

@asf-gitbox-commits
Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor

@JingsongLi JingsongLi left a comment

Choose a reason for hiding this comment

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

This is an ASF infrastructure PR for setting up default branch rulesets. It adds branch protection via .asf.yaml and will auto-merge on 2026-06-14 if no action is taken.

The change is minimal (+13 lines to .asf.yaml) and follows standard ASF security defaults. No concerns from a code perspective — this is infra governance.

@JingsongLi
Copy link
Copy Markdown
Contributor

+1

@JingsongLi JingsongLi merged commit f4dc163 into master May 24, 2026
22 of 24 checks passed
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.

2 participants