Skip to content

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

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

[INFRA] Set up default rulesets for default and release branches#1
THausherr 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

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds an Apache Software Foundation .asf.yaml configuration to apply GitHub branch rulesets that align the repository with ASF “sane default security settings” for the default branch and release branches.

Changes:

  • Introduces a GitHub branch ruleset named “Default Branch Protection”.
  • Applies the ruleset to ~DEFAULT_BRANCH, release/*, and rel/*, with root team bypass.
  • Disables branch deletion and force-push for the protected branch patterns.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@THausherr THausherr merged commit 0361b5c into master May 16, 2026
1 check 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.

3 participants