Skip to content

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

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

[INFRA] Set up default rulesets for default and release branches#4812
asf-gitbox-commits wants to merge 1 commit into
trunkfrom
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

@smiklosovic
Copy link
Copy Markdown
Contributor

smiklosovic commented May 18, 2026

I am not completely sure about this. Sometimes we do want to force-push to trunk, in cases when somebody merges up wrongly or pushes commits which should not be there at all / were committed by mistake etc. This already happened in the past. Not being able to force-push in these situations is not ideal.

There is nothing wrong with not being able to delete a release / trunk branch. No objections there.

@smiklosovic
Copy link
Copy Markdown
Contributor

@michaelsembwever @driftx opinions?

@driftx
Copy link
Copy Markdown
Contributor

driftx commented May 18, 2026

maybe hit the ML about force pushing?

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