feat(ci): run E2E Staging Canvas on staging branch pushes
Add `staging` to push/pull_request branches in e2e-staging-canvas.yml so the auto-promote gate check (`--event push --branch staging`) can find a completed run for this workflow. Without this, the E2E Staging Canvas gate is structurally impossible to satisfy from staging pushes. Mirrors what PR #1891 does for e2e-api.yml — completing the two-part fix for the auto-promote gate gap (issue tracking: auto-promote blocked because both E2E gate workflows only fired on main). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
307b5b5408
commit
9cd4e06a78
9
.github/workflows/e2e-staging-canvas.yml
vendored
9
.github/workflows/e2e-staging-canvas.yml
vendored
@ -5,18 +5,21 @@ name: E2E Staging Canvas (Playwright)
|
||||
# e2e-staging-saas.yml (which tests the API shape) by exercising the
|
||||
# actual browser + canvas bundle against live staging.
|
||||
#
|
||||
# Triggers: push to main or PR touching canvas sources + this workflow,
|
||||
# Triggers: push to main/staging or PR touching canvas sources + this workflow,
|
||||
# manual dispatch, and weekly cron to catch browser/runtime drift even
|
||||
# when canvas is quiet.
|
||||
# Added staging to push/pull_request branches so the auto-promote gate
|
||||
# check (--event push --branch staging) can see a completed run for this
|
||||
# workflow — mirrors what PR #1891 does for e2e-api.yml.
|
||||
|
||||
on:
|
||||
push:
|
||||
branches: [main]
|
||||
branches: [main, staging]
|
||||
paths:
|
||||
- 'canvas/**'
|
||||
- '.github/workflows/e2e-staging-canvas.yml'
|
||||
pull_request:
|
||||
branches: [main]
|
||||
branches: [main, staging]
|
||||
paths:
|
||||
- 'canvas/**'
|
||||
- '.github/workflows/e2e-staging-canvas.yml'
|
||||
|
||||
Loading…
Reference in New Issue
Block a user