You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cleanup-branches.yml has invalid YAML (missing steps: key), breaking lint:yaml for every PR #1074
.github/workflows/cleanup-branches.yml, introduced in #1067, is missing the steps: key under the cleanup job. The env: mapping is immediately followed by a - name: Checkout repository list item with no steps: parent key, which is invalid YAML.
Because npm run lint:all runs spectral lint '**/*.{yml,yaml}' across the whole repo (not just changed files), this breaks the lint job - and therefore the required All Checks Passed status check - for every PR into develop, regardless of what the PR actually touches. Found while trying to get an unrelated PR (#1073) green.
To Reproduce
npm run lint:all on current develop
See parser errors at .github/workflows/cleanup-branches.yml:37-46 ("Bad indentation of a mapping entry", "Can not read a block mapping entry")
Expected behavior
cleanup-branches.yml parses as valid YAML and npm run lint:all passes.
Additional Context
Fix: insert steps: before the - name: Checkout repository line, at the same indentation as the job's other top-level keys (runs-on, env).
Fixed by #1075 (merged: a3a327c). GitHub's auto-close via the "Closes #1074" reference didn't fire despite correctly recognizing the link (confirmed via the GraphQL closingIssuesReferences field) — closing manually.
Re-closing. The prior reopen appears to have used a stale/delayed workflow run evaluating the issue as it was before the DoR/DoD sections were added and the status:needs-more-info label removed. Current body and labels meet the close requirements.
Activity
linear-code commentedon Jul 22, 2026
LS-1632
github-actions commentedon Jul 22, 2026
✅ Template check passed after update. Thanks for fixing the issue body.
docs(changelog): add entry for cleanup-branches.yml YAML fix
ashleyshaw commentedon Jul 22, 2026
Fixed by #1075 (merged: a3a327c). GitHub's auto-close via the "Closes #1074" reference didn't fire despite correctly recognizing the link (confirmed via the GraphQL
closingIssuesReferencesfield) — closing manually.ashleyshaw commentedon Jul 22, 2026
Re-closing. The prior reopen appears to have used a stale/delayed workflow run evaluating the issue as it was before the DoR/DoD sections were added and the status:needs-more-info label removed. Current body and labels meet the close requirements.
fix(ci): re-fetch live issue state in template-enforcement guards
fix(ci): re-fetch live issue state in template-enforcement guards
fix(ci): re-fetch live issue state in template-enforcement guards
fix(ci): re-fetch live issue state in template-enforcement guards (#1086