The crewing module is built as a stack of feature-flagged phases that land on feat/crewing-foundations (the integration branch) before the whole thing merges to master. PRs into that branch were skipped because pr-checks only triggered on `branches: [master]`. Add feat/crewing-foundations so each stacked phase PR runs the same hard gates (test-presence policy, type-check, unit + integration). For pull_request events the workflow is read from the base branch, so this must live on feat/crewing-foundations to take effect for PRs targeting it. |
||
|---|---|---|
| .. | ||
| deploy.yml | ||
| pr-checks.yml | ||
| staging.yml | ||