• Restore push trigger to all branches for pre-PR CI visibility
• Add concurrency group to cancel duplicate workflow runs
• Prevent redundant CI execution on push and pull_request events

Expand push trigger and add concurrency deduplication

• Changed push trigger from master branch only to "**" (all branches)
• Added concurrency configuration with group based on workflow and branch name
• Enabled cancel-in-progress to terminate duplicate runs when both push and pull_request events
 trigger

.github/workflows/CI.yml

Description

Because workflow-level cancel-in-progress: true uses the same concurrency group for all events, a
scheduled run on the default branch can be canceled if a push-triggered run on that branch starts
while the schedule is still executing. This can intermittently prevent scheduled CI from completing
and reduce periodic signal.

Code

.github/workflows/CI.yml[R16-18]

+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+  cancel-in-progress: true

Evidence

The workflow defines both a nightly schedule trigger and a workflow-level concurrency policy with
cancel-in-progress: true. For scheduled runs github.head_ref is empty, so the group falls back
to github.ref_name (the default branch ref), which can match the group used by push runs on that
same branch and lead to cancellation if they overlap in time.

.github/workflows/CI.yml[12-18]
.github/workflows/CI.yml[4-6]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The workflow-level concurrency cancellation applies to `schedule` events too, so the nightly run can be canceled by a concurrently-started push run on the default branch.

### Issue Context
We want to cancel duplicate push/pull_request runs, but scheduled runs are periodic signal and usually should be allowed to complete.

### Fix Focus Areas
- .github/workflows/CI.yml[12-18]

### Suggested change
Make schedule runs use a distinct group and disable cancel-in-progress for them, e.g.:

```yaml
concurrency:
 group: ${{ github.workflow }}-${{ github.event_name == 'schedule' && 'schedule' || (github.head_ref || github.ref_name) }}
 cancel-in-progress: ${{ github.event_name != 'schedule' }}
```

This preserves duplicate-cancellation for push/PR while keeping scheduled runs reliable.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools