This is an automated email from the ASF dual-hosted git repository.

Yicong-Huang pushed a commit to branch release/v1.1.0-incubating
in repository https://gitbox.apache.org/repos/asf/texera.git


The following commit(s) were added to refs/heads/release/v1.1.0-incubating by 
this push:
     new 666b3fe535 fix(ci): preserve in-progress runs on release/* branches 
(#4883)
666b3fe535 is described below

commit 666b3fe535753777be95151724eb69edd02a77c6
Author: Yicong Huang <[email protected]>
AuthorDate: Mon May 4 05:22:53 2026 +0000

    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?
    
    (backported from commit 332d4f4f8d1938f7a3fe41033fe97ed41d44d673)
    
    Generated-by: Claude Code (Opus 4.7)
---
 .github/workflows/required-checks.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/required-checks.yml 
b/.github/workflows/required-checks.yml
index af4fcc9ea8..e7b8968ca4 100644
--- a/.github/workflows/required-checks.yml
+++ b/.github/workflows/required-checks.yml
@@ -39,7 +39,7 @@ permissions:
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' && 
!startsWith(github.ref, 'refs/heads/release/') }}
 
 jobs:
   # Precheck decides which downstream jobs run for this event:

Reply via email to