Vance Ingalls 05b135ceda 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`.

2026-04-22 17:28:11 -07:00

..

ISSUE_TEMPLATE

docs: add prompt cookbook + prompting guide for AI agents (#286)

2026-04-15 22:22:46 -07:00

workflows

ci: subscribe to edited PR events so workflows re-fire after Graphite restacks

2026-04-22 17:28:11 -07:00

pull_request_template.md

chore: initial repo setup with README, LICENSE, and contributor docs

2026-03-10 01:57:55 +00:00

renovate.json

ci: skip PR runs when targeting a non-main base branch (#426)

2026-04-22 14:19:04 -07:00