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
fix(pr-pipeline): issue lane runs check-affected before pushing so lane PRs don't open red #8310
Attended Build hand-fixed red lane PRs (#7892, #7932, #7940, #7942, 2026-10-18). Every failure was one the lane could have caught before pushing: skill-name registry entries, cheatsheet metadata, /home/<user> paths in eval fixtures, typos, and shellcheck SC2016. 36 red lane PRs remain.
Remove the cause instead of fixing it after the fact: the issue lane (work-resolve-issue) runs scripts/check-affected.sh on its change before it pushes, and fixes what it finds in the same run. fix-ci (#7031) stays as the fallback for anything that still turns red.
Note: most lane branches are about 140-150 commits behind main, so the pre-push stale-base hook will also ask for a merge. The lane should merge main first.
Activity
github-actions commentedon Oct 18, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Proposed work class: work-class: scoped
Basis: automated intake triage; a maintainer confirms or changes it.
Automated triage. A maintainer reviews it.