Yicong-Huang opened a new pull request, #7123:
URL: https://github.com/apache/texera/pull/7123

   ### What changes were proposed in this PR?
   
   Change the `Restrict Branch Creation` ruleset exclude from 
`refs/heads/gh-readonly-queue/*` to `refs/heads/gh-readonly-queue/**`.
   
   GitHub ruleset globs do not cross `/`, so a single `*` only matches one path 
segment. Merge queue temporary branches nest the base ref 
(`gh-readonly-queue/main/pr-N`, `gh-readonly-queue/release/v1.2/pr-N`), so they 
were **not** excluded — the `creation` rule blocked the queue from creating 
them, freezing merges to `main` and every release branch. `**` matches all 
depths and restores the queue.
   
   > ⚠️ The repo-wide merge queue is currently frozen by this very bug, so this 
PR cannot merge through the queue. It needs ASF Infra (admin) to admin-merge 
it, or to temporarily disable the `Restrict Branch Creation` ruleset so the 
queue drains and this PR merges normally.
   
   ### Any related issues, documentation, discussions?
   
   Regression from #7121, which activated the `Restrict Branch Creation` 
ruleset. Unblocks backport PRs such as #7101.
   
   ### How was this PR tested?
   
   Verified against the live repo via `GET 
/repos/apache/texera/rules/branches/...`: the `creation` rule still applies to 
the multi-segment `gh-readonly-queue/main/pr-1` and 
`gh-readonly-queue/release/v1.2/pr-7101` (not matched by `/*`), while the 
single-segment `gh-readonly-queue/foo` is excluded. Ran the asfyaml normalizer 
over `.asf.yaml` to confirm the ruleset resolves with `exclude` ending in 
`refs/heads/gh-readonly-queue/**`.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 4.8)
   


-- 
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]

Reply via email to