pipeline.yml was in CI's paths-ignore, so PRs that only touch pipeline.yml never trigger CI — but 'build' is a required status check, deadlocking those PRs forever. This also means pipeline.yml changes merge without any code validation, which is how the dev-publish 'next: not found' bug slipped through in the first place. |
||
|---|---|---|
| .. | ||
| ai-triage.yml | ||
| build-native.yml | ||
| ci.yml | ||
| cleanup-dev-versions.yml | ||
| pipeline.yml | ||
| pr-risk.yml | ||