mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-16 06:19:21 +00:00
ci: subscribe to edited PR events so workflows re-fire after Graphite restacks
Workflows that gate `pull_request` on `branches: [main]` are silently skipped for the head-ref push that `gt submit` makes during a stack restack: Graphite momentarily flips the PR's base off of `main` before resetting it back, and GitHub does not re-evaluate `pull_request` triggers on `base_ref_changed` events with the default activity types. The result: required checks (Build, Typecheck, Test: runtime contract, Windows render, Windows tests, Semantic PR title) never run for that head SHA and the PR sits in BLOCKED forever — even when the head matches a green commit on `main`. PR #396 hit this exact pattern after #426 added the `branches: [main]` filters. Adding `edited` to the activity types causes the workflow to re-fire when the base is set back to `main`. The existing `branches: [main]` filter still rejects intermediate stack PRs, preserving #426's intent of skipping CI on stack PRs that aren't yet targeting `main`.
This commit is contained in:
@@ -8,6 +8,12 @@ name: Windows render verification
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
# `edited` is required so the workflow re-fires when a PR's base ref is
|
||||
# set back to `main` after a Graphite stack restack momentarily flips
|
||||
# the base off of `main`. Without it, `pull_request` triggers are not
|
||||
# re-evaluated on `base_ref_changed`, leaving required checks skipped
|
||||
# for that head SHA forever.
|
||||
types: [opened, synchronize, reopened, edited]
|
||||
branches: [main]
|
||||
push:
|
||||
branches: [main]
|
||||
|
||||
Reference in New Issue
Block a user