mengw15 opened a new pull request, #8624: URL: https://github.com/apache/texera/pull/8624
### What changes were proposed in this PR? GitHub will not create the `Merge Queue (release)` ruleset #8379 added. asfyaml has rejected it on every push to main since that PR merged — 38 mails to `commits@` so far, the first 49 seconds after the merge: ``` Validation failed while creating ruleset 'Merge Queue (release)': ['Actor GitHub Actions integration must be part of the ruleset source or owner organization'] ``` The fail-safe ordering #8379 built held: the apply aborts on that ruleset, so `Merge Queue` was never shrunk and the release branches were never left uncovered. But it also means `GET /repos/apache/texera/rulesets` still returns exactly the four rulesets from before #8379, and — because the abort takes the whole `github` feature with it — nothing in `.asf.yaml`'s `github:` block has been applied to this repo since 2026-09-11. The next label, notification or collaborator change would merge, do nothing, and say so only on a list its author does not read. This restores the file to what GitHub actually holds. #8379 also narrowed the `push-backports` job to `actions`, `contents`, `issues` and `statuses`. Commenting on a pull request is scoped by `pull-requests`, not `issues`, so since 2026-09-11 the step that annotates the original PR when a backport fails has taken four 403s and given up with a warning — leaving the step green. The 2026-09-03 failures (#8347, #8343) did comment and were noticed; #8432, #8494 and #8562 did not, and sat unnoticed until the v1.3 audit. The scope goes back. This does not revive the backport fast path — that push stays rejected, as it has been since 2026-07-24. Routing a clean backport through a pull request instead is #8378's job, and #8377 stays open until it lands. ### Any related issues, documentation, discussions? Relates to #8377 (closed by #8379, not actually fixed) and #8379. ### How was this PR tested? `.github/scripts/test_asf_rulesets.sh` is green on the result (25 files duplicate-key clean, 4 rulesets checked). Both of its remaining invariants were verified red first: adding an `Integration` bypass to a ruleset that covers `~DEFAULT_BRANCH` fails it, and a duplicated `jobs:` key in a workflow fails it, each with exit 1. The `.asf.yaml` change is byte-identical to the state before #8379 — the file was not touched between that PR and this one — so applying it asks asfyaml for exactly the configuration GitHub already has. ### Was this PR authored or co-authored using generative AI tooling? Yes. Generated-by: Claude Code (claude-opus-5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
