Skip to content

ci: gate tests and desktop smoke on PRs into release/** and hotfix/**#82

Merged
webup merged 1 commit into
release/0.3.0from
ci/gate-tests-on-release-prs
Apr 23, 2026
Merged

ci: gate tests and desktop smoke on PRs into release/** and hotfix/**#82
webup merged 1 commit into
release/0.3.0from
ci/gate-tests-on-release-prs

Conversation

@webup
Copy link
Copy Markdown
Contributor

@webup webup commented Apr 23, 2026

What

Add `release/` and `hotfix/` to the `pull_request.branches` list in `test.yml` and `desktop-e2e.yml`, so the same CI gates that run on PRs to `main`/`develop` also run on PRs into release and hotfix branches.

Why

Today `test.yml` and `desktop-e2e.yml` trigger on `pull_request` only for `main` and `develop` (test) or `main` (desktop smoke). That means PRs targeting `release/0.3.0` — including rc stabilization fixes like #81 — only get the lightweight `pr-description-check.yml` run. Tests only execute on push after merge, when failures are more expensive to fix. Adding the release/hotfix branches here closes that gap so rc PRs get the same validation as PRs into `develop`.

Scope

  • `test.yml` — `pull_request.branches` gains `'release/', 'hotfix/'`
  • `desktop-e2e.yml` — same
  • `build.yml` intentionally skipped — its PR trigger is already scoped to `main` (for the final release→main PR). Desktop bundles are expensive cross-platform builds, and the post-merge `push: branches: ['release/', 'hotfix/']` trigger already catches bundle failures before tag.

Target branch

`release/0.3.0` — lands first where it's immediately useful for rc.2 stabilization; forward-propagates into `main` and `develop` via the standard release merges at 0.3.0 GA.

Test plan

  • YAML syntactically valid (two-line changes, same shape as existing entries)
  • After merge, open a trivial follow-up PR into `release/0.3.0` and verify `test.yml` + `desktop-e2e.yml` now run.

🤖 Generated with Claude Code

PRs targeting release/* or hotfix/* currently only run the description
check — test.yml and desktop-e2e.yml are gated to PRs against main or
develop. That leaves rc stabilization PRs (like fix/* → release/0.3.0)
unvalidated until after merge. Add release/** and hotfix/** to each
workflow's pull_request.branches list so the same gates apply.

build.yml intentionally skipped: desktop bundles are expensive
cross-platform builds; post-merge push-to-release already catches
bundle failures before tag.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@webup webup merged commit c2cf7b1 into release/0.3.0 Apr 23, 2026
13 checks passed
@webup webup deleted the ci/gate-tests-on-release-prs branch April 23, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant