|
| 1 | +# CI Force-Run Sentinel |
| 2 | + |
| 3 | +Every path-filtered CI workflow under `.github/workflows/` lists this file |
| 4 | +in its `paths:` filter (or, for workflows with an internal `check_changes` |
| 5 | +gate, in its diff allowlist). Editing this file forces those workflows to |
| 6 | +run on the next push, which is useful when: |
| 7 | + |
| 8 | +- Migrating tooling (package manager, Node version, monorepo runner) |
| 9 | +- Refactoring shared `.github/actions/*` composite actions |
| 10 | +- Pre-merge confidence check on a large branch |
| 11 | +- Verifying that a workflow you _think_ is unrelated to your changes still |
| 12 | + passes |
| 13 | + |
| 14 | +## Scope and limitations |
| 15 | + |
| 16 | +- Triggers path-filtered `pull_request` / `push` workflows only. |
| 17 | +- Does **not** trigger workflows gated on `workflow_dispatch` / `schedule` |
| 18 | + only (e.g. `release-calendar.yml`), nor workflows whose `push:` event |
| 19 | + filters this branch out (e.g. `npm-publish.yml` only runs on `push` to |
| 20 | + `dev`). |
| 21 | +- Jobs guarded by `if: github.event.pull_request.head.repo.fork == false` |
| 22 | + still skip on fork PRs by design (secrets are not exposed to forks). |
| 23 | +- Jobs hard-disabled with `if: false` stay disabled regardless of the |
| 24 | + sentinel. |
| 25 | + |
| 26 | +Run `python3 scripts/ci/add-force-run-sentinel.py --check` to verify that |
| 27 | +every workflow with a `paths:` block lists this sentinel and that internal |
| 28 | +`check_changes` allowlists include it too. |
| 29 | + |
| 30 | +## How to use |
| 31 | + |
| 32 | +1. Add a one-line entry to the log below with date + reason. |
| 33 | +2. Commit on your branch. Path-filtered CI workflows will run on the PR. |
| 34 | +3. After verification, you may revert the entry before merge (optional — |
| 35 | + the file is intentionally low-churn; leaving entries as a history is |
| 36 | + also fine). |
| 37 | + |
| 38 | +## Log |
| 39 | + |
| 40 | +- 2026-05-13 — Force-run all workflows to verify Yarn → pnpm migration |
| 41 | + (PR #2069). |
| 42 | +- 2026-05-13 — Re-trigger after enabling check_changes sentinel + debug |
| 43 | + step + re-enabling web/workspace jobs (PR #2069). |
0 commit comments