From 5991a2c8b088ae940c22d14d5e55ff6c2e710e06 Mon Sep 17 00:00:00 2001 From: Garrett Delfosse Date: Wed, 27 May 2026 14:46:18 -0400 Subject: [PATCH] ci: trigger CI on release branch creation (#25744) GitHub Actions does not reliably trigger the push-based CI workflow when a new branch is created at a commit that already has a workflow run from another branch (e.g. `main`). This meant cutting a release branch produced no CI run on it, so `should_deploy.sh` never got to approve the deploy from the release branch. Adds the `create` event trigger to `ci.yaml` with a condition on the `changes` job to only proceed for release branch creations. All other jobs depend on `changes`, so non-release branch creations are a no-op. > Generated with [Coder Agents](https://coder.com/agents) by @f0ssel --- .github/workflows/ci.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index f0a7ccd76c..78d6aba61a 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -6,6 +6,13 @@ on: - main - release/* + # GitHub Actions does not reliably trigger push-based CI when a new + # branch is created at a commit that already has a workflow run (e.g. + # from main). The create event fires separately and ensures CI runs + # on newly cut release branches. Non-release branch creations are + # filtered out by the changes job condition. + create: + pull_request: workflow_dispatch: @@ -21,6 +28,13 @@ concurrency: jobs: changes: runs-on: ubuntu-latest + # For create events, only run on release branches to avoid + # triggering CI for every feature branch creation. + if: | + github.event_name != 'create' || ( + github.event.ref_type == 'branch' && + startsWith(github.event.ref, 'release/') + ) outputs: docs-only: ${{ steps.filter.outputs.docs_count == steps.filter.outputs.all_count }} docs: ${{ steps.filter.outputs.docs }}