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
scripts/pr-queue-hygiene.mjs — the 48h stale-conflict gate that labels conflicting PRs needs-rebase-or-close and posts nag comments — is invoked by no workflow. It has been dead code since the day it landed.
grep -rn 'pr-queue-hygiene' .github/ → no matches (main @ 0fd5f8b).
git log --all -- '.github/workflows/*hygiene*' → empty: a hygiene workflow never existed.
The script's own usage comment claims the opposite: "Requires gh authenticated with pull-requests: write on this repo (as the workflow already grants)" — the workflow it references does not exist.
The repo has exactly 5 workflows (ci.yml, create-milestones.yml, deploy-gh-pages.yml, import-architectures.yml, refresh-community-people.yml); none runs it, and npm run pr-queue-hygiene is reachable from nothing.
Impact
Two rounds of hardening have landed (and a third is in flight) on a code path that never executes:
Meanwhile the queue problem the script exists to solve is real: #81 tracks 50+ stranded mergeable PRs, and the collision issues (#372–#380) document the churn an un-run hygiene job was supposed to tame. Every PR that stops conflicting keeps its stale marker forever; every PR conflicting >48h goes un-nagged; the needs-rebase-or-close label is never applied or removed.
First run should use DRY_RUN=1 to preview label/comment actions before going live.
Needs a human with maintainer credentials, or an agent whose App installation has Workflows read/write — the contributor-tier App token cannot push under .github/workflows/** (same constraint recorded in #428 / #444).
Filed by scanner agent (ACMM L4 — issues-only mode)
Finding
scripts/pr-queue-hygiene.mjs— the 48h stale-conflict gate that labels conflicting PRsneeds-rebase-or-closeand posts nag comments — is invoked by no workflow. It has been dead code since the day it landed.grep -rn 'pr-queue-hygiene' .github/→ no matches (main @ 0fd5f8b).git log --all -- '.github/workflows/*hygiene*'→ empty: a hygiene workflow never existed.ghauthenticated withpull-requests: writeon this repo (as the workflow already grants)" — the workflow it references does not exist.ci.yml,create-milestones.yml,deploy-gh-pages.yml,import-architectures.yml,refresh-community-people.yml); none runs it, andnpm run pr-queue-hygieneis reachable from nothing.Impact
Two rounds of hardening have landed (and a third is in flight) on a code path that never executes:
ci: fix pr-queue-hygiene mergeable check…) with no workflow.Meanwhile the queue problem the script exists to solve is real: #81 tracks 50+ stranded mergeable PRs, and the collision issues (#372–#380) document the churn an un-run hygiene job was supposed to tame. Every PR that stops conflicting keeps its stale marker forever; every PR conflicting >48h goes un-nagged; the
needs-rebase-or-closelabel is never applied or removed.Recommendation
Add
.github/workflows/pr-queue-hygiene.yml, e.g.:First run should use
DRY_RUN=1to preview label/comment actions before going live.Needs a human with maintainer credentials, or an agent whose App installation has Workflows read/write — the contributor-tier App token cannot push under
.github/workflows/**(same constraint recorded in #428 / #444).Filed by scanner agent (ACMM L4 — issues-only mode)
🐝 Hive Agent:
scanner| Instance:hosted-available-lke648397-260827-5n31| SHA:0fd5f8b— hive: agent=scanner backend=copilot model=kimi-k3