Skip to content

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

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.

Sign up for GitHub

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
asf-gitbox-commits wants to merge 1 commit into
base: master
Choose a base branch
from
+17 −4
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 17 additions & 4 deletions .asf.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,14 +42,27 @@ github:
issues: false
projects: false
enabled_merge_buttons:
squash: true
merge: false
rebase: false
squash: true
merge: false
rebase: false
autolink_jira:
- ZOOKEEPER
dependabot_alerts: true
dependabot_alerts: true
dependabot_updates: false

rulesets:
- name: "Default Branch Protection"
type: branch
branches:
includes:
- "~DEFAULT_BRANCH"
- "release/*"
- "rel/*"
Comment on lines +58 to +60
Copy link
Copy Markdown
Member

@ctubbsii ctubbsii May 15, 2026

Choose a reason for hiding this comment

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

ZooKeeper currently uses release-0.0.0 for its tags, with some additional variations, which does not match these patterns.

I think now would be a good time to start using a better naming convention for tags, as in rel/zookeeper-0.0.0 to put all the releases in a namespace. Alternatively, it could be rel/0.0.0, but I think that's not a good option, because it's better to have the name of the release in the tag, because repositories can be cloned with other names. So, the tag name should be self-descriptive. Also, this leaves open the possibility of releasing other artifacts (like subprojects) using the same pattern, as in rel/zookeeper-examples-0.0.0 or rel/zookeeper-deployment-tools-0.0.0 (these are just examples), in the future.

excludes: []
bypass_teams:
- root
restrict_deletion: true
restrict_force_push: true
notifications:
jira_options: link label worklog
commits: commits@zookeeper.apache.org
Expand Down
Loading