The GitHub Actions job "Required Checks" on texera.git/main has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 332d4f4f8d1938f7a3fe41033fe97ed41d44d673 / Yicong Huang <[email protected]> fix(ci): preserve in-progress runs on release/* branches (#4883) ### What changes were proposed in this PR? Extend the `cancel-in-progress` exemption in `required-checks.yml` so it covers `release/**` branches in addition to `main`. Both branches show up in the `push:` trigger and share the same "production" risk profile — a back-to-back push (e.g. when a backport applies a follow-up commit) currently cancels the prior in-progress run mid-flight, leaving release branches with incomplete CI signal. ```yaml cancel-in-progress: ${{ github.ref != 'refs/heads/main' && !startsWith(github.ref, 'refs/heads/release/') }} ``` PR head (feature branches), `ci-enable/**`, and `workflow_dispatch` on non-protected refs continue to cancel-in-progress as before. ### Any related issues, documentation, discussions? Closes #4882 ### How was this PR tested? The change is a single-line GitHub expression edit; static-validated by `python3 -c 'import yaml; yaml.safe_load(open(...))'`. Behavior is contract-tested by GitHub's expression engine semantics (the existing `${{ github.ref != 'refs/heads/main' }}` form is just being conjoined with a `startsWith` check). Manual end-to-end verification will be done after merge by pushing two commits back-to-back to a `release/*` branch and confirming the first run completes instead of being cancelled. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Report URL: https://github.com/apache/texera/actions/runs/25302511956 With regards, GitHub Actions via GitBox
