Required Checks workflow cancels in-progress runs on release/* branches

[Yicong-Huang]

What happened?

.github/workflows/required-checks.yml:42 sets

cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}

The push: trigger of this workflow lists main, ci-enable/**, and release/**. The expression only exempts main, so a back-to-back push to a release/** branch (e.g. when a backport applies a follow-up commit) cancels the prior in-progress run via concurrency-group cancellation. Release branches share main's "production" risk profile — partial CI signal there means the cancelled run's check_runs may end up reflecting an incomplete picture of what was tested.

How to reproduce?

1. Push commit A to release/v1.1.0-incubating. Required Checks starts.
2. Before that run finishes, push commit B to the same branch.
3. Observe: the run for A is cancelled mid-flight (concurrency group Required Checks-refs/heads/release/v1.1.0-incubating, cancel-in-progress: true); only B's run completes.

Branch

main

Commit Hash (Optional)

1bf18e7