Trigger CI workflows on all release/** branches#2117
Merged
Conversation
Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates GitHub Actions workflow triggers so CI and related checks run for pull requests and pushes targeting any current/future release/** branches, avoiding stale hardcoded release branch filters.
Changes:
- Updated
ci.yamlto trigger onmainandrelease/**for bothpushandpull_request. - Updated
ui-chromatic.yamlto trigger onmainandrelease/**for bothpushandpull_request. - Expanded
migration-immutability.yamlandsqlc-generate-check.yamlpull_requestbranch filters to includerelease/**.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/ci.yaml | Broadens CI triggers to include all release/** branches for pushes and PRs. |
| .github/workflows/ui-chromatic.yaml | Broadens UI Storybook/Chromatic triggers to include all release/** branches for pushes and PRs. |
| .github/workflows/migration-immutability.yaml | Runs migration immutability checks on PRs targeting release branches as well as main. |
| .github/workflows/sqlc-generate-check.yaml | Runs sqlc generation checks on PRs targeting release branches as well as main. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
EItanya
approved these changes
Jun 30, 2026
iplay88keys
added a commit
that referenced
this pull request
Jun 30, 2026
## Summary Backport of #2117 to `release/v0.9.x`: switch the workflow branch filters from hardcoded release names to a `release/**` glob so CI actually runs on PRs targeting this release branch. Cherry-pick of `83c8ae96` (`-x` provenance recorded). ## Why this is needed on the release branch Workflow `branches` filters are per-branch. `release/v0.9.x`'s copies still read `[main, release/v0.7.x]` (or `[main]`), so PRs targeting `release/v0.9.x` trigger no CI — only branch-agnostic checks (DCO/labelers/snyk) run. The `main` fix in #2117 does not affect this branch on its own; existing release branches carry their own filters and must have the change backported. ## Changes `branches` filters updated to `[main, "release/**"]`: - `ci.yaml` — push + pull_request - `ui-chromatic.yaml` — push + pull_request - `migration-immutability.yaml` — pull_request - `sqlc-generate-check.yaml` — pull_request Trigger filters only; no job logic changed. The glob still matches `release/v0.7.x`, so nothing that ran before stops. Signed-off-by: Jeremy Alvis <jeremy.alvis@solo.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Switch the workflow branch filters from hardcoded release branch names to a
release/**glob, so CI runs on every release branch instead of only the one that happened to be current when the filter was last edited.Why
The filters hardcoded
release/v0.7.x(or weremain-only).release/v0.7.xis long superseded, so PRs targeting current release branches — e.g.release/v0.9.x— triggered no CI (only branch-agnostic checks like DCO/labelers/snyk ran). Arelease/**glob matches every current and future release branch, so this won't go stale on the next release cut.Changes
branchesfilters updated to[main, "release/**"]:ci.yaml— push + pull_request (was[main, release/v0.7.x])ui-chromatic.yaml— push + pull_request (was[main, release/v0.7.x])migration-immutability.yaml— pull_request (was[main])sqlc-generate-check.yaml— pull_request (was[main])No job logic changed — only the trigger branch filters. The glob still matches
release/v0.7.x, so nothing that ran before stops running.migration-immutabilityandsqlc-generate-checkweremain-only and now also run on release-branch PRs (those checks are relevant to release branches too).Notes
pull_request, GitHub evaluates the trigger from the PR head's workflow file, so this takes effect for PRs cut frommainonce merged, and for future release branches cut frommain.release/v0.9.x) for their PRs to get CI.