This is an automated email from the ASF dual-hosted git repository.
Yicong-Huang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/texera.git
The following commit(s) were added to refs/heads/main by this push:
new 875616561f ci: opt in to .asf.yaml rulesets staged rollout (#4604)
875616561f is described below
commit 875616561f3cbcc77e7b86d6a02b5ac1c5f706f5
Author: Yicong Huang <[email protected]>
AuthorDate: Fri May 1 01:22:23 2026 -0700
ci: opt in to .asf.yaml rulesets staged rollout (#4604)
### What changes were proposed in this PR?
Add a `meta:` block to `.asf.yaml` that opts the repository in to the
staged rollout of the asfyaml `rulesets:` directive:
```yaml
meta:
environment: github_rulesets
```
Without this, the `Release Branch Protection` ruleset added in #4582 is
silently skipped: the strictyaml schema accepts `rulesets:`, but
`asfyaml/feature/github/rulesets.py` early-returns unless
`github_rulesets` is in `environments_enabled`.
### Any related issues, documentation, discussions?
- Closes #4603
- Follow-up to #4579 / #4582 (the ruleset config is already in
`.asf.yaml`; this PR makes it actually run)
- Verified the gap via the GitHub API:
- `GET /repos/apache/texera/rulesets` → `[]`
- `GET /repos/apache/texera/rules/branches/release/v1.1.0-incubating` →
`[]`
- Verified the gating in `apache/infrastructure-asfyaml` source:
- Schema accepts `rulesets:` (`asfyaml/feature/github/__init__.py`)
- Directive gated on `github_rulesets` env flag
(`asfyaml/feature/github/rulesets.py`, commit `8d2ca2c2` — \"Gate
rulesets directive behind github_rulesets environment for staged
rollout\")
- `meta.environment` is added to `environments_enabled`
(`asfyaml/asfyaml.py`)
### How was this PR tested?
- Diff is a 6-line addition to `.asf.yaml`; no code paths are exercised
locally.
- After merge, the expected outcome is that ASF Infra reconciles the
existing `Release Branch Protection` ruleset into the repo. Verification
plan post-merge:
- `gh api repos/apache/texera/rulesets` should return one entry named
`Release Branch Protection`
- `gh api repos/apache/texera/rules/branches/release/v1.1.0-incubating`
should list the required status checks and PR-review rule
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7
---
.asf.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/.asf.yaml b/.asf.yaml
index 00cd7b1089..097d76eb3e 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -17,6 +17,12 @@
# https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
+meta:
+ # Opt in to the staged rollout of the asfyaml `rulesets:` directive.
+ # See apache/infrastructure-asfyaml asfyaml/feature/github/rulesets.py — the
+ # directive is gated on the `github_rulesets` environment flag.
+ environment: github_rulesets
+
github:
description: "Collaborative Machine-Learning-Centric Data Analytics Using
Workflows"
homepage: https://texera.io/
