Closed issue #17 still carries blocked:needs-attention label #45

New issue

Closed

opened 2026-08-14 03:28:22 +00:00 by Mark · 1 comment

Mark commented

2026-08-14 03:28:22 +00:00

Owner

devforge#17 (Webhook notifications) is closed (2026-08-08T08:57:51Z) with fix commits ceb6591c1a / 6ceafc62f5 on main, but it still carries the blocked:needs-attention label — never cleared after the re-close. The label is a pipeline artifact from the false-positive-close detection that reopened #17 on 08-08 with "no fix commit exists on master"; that check looked at a non-existent master branch (default branch is main).

Action: clear blocked:needs-attention from closed #17. Separately, the false-positive-close detection path that emits "exists on master" should use the repo's default branch, not a hardcoded master (the current janitor-kanban-sync.py already uses default_branch — verify which reopen path produced the master text).

Kanban card: t_223849fd (probe finding 4, follow-up to closed Mark/devforge#17).

devforge#17 (Webhook notifications) is closed (2026-08-08T08:57:51Z) with fix commits ceb6591c1a / 6ceafc62f5 on main, but it still carries the blocked:needs-attention label — never cleared after the re-close. The label is a pipeline artifact from the false-positive-close detection that reopened #17 on 08-08 with "no fix commit exists on master"; that check looked at a non-existent master branch (default branch is main). Action: clear blocked:needs-attention from closed #17. Separately, the false-positive-close detection path that emits "exists on master" should use the repo's default branch, not a hardcoded master (the current janitor-kanban-sync.py already uses default_branch — verify which reopen path produced the master text). Kanban card: t_223849fd (probe finding 4, follow-up to closed Mark/devforge#17).

Mark added the

chore

label

2026-08-14 03:28:22 +00:00

Mark commented

2026-08-14 05:17:07 +00:00

Author

Owner

Chore complete: blocked:needs-attention cleared from closed #17 (verified labels=[]), and the false-positive-close reopen path that emitted "no fix commit exists on master" was identified as the forgejo-false-positive-close-detection skill recipe (hardcoded master). Patched the recipe to resolve the repo default_branch (main) for both the commit scan and the reopen comment. Live scripts (janitor-kanban-sync.py, janitor-kanban-reconciler.py) already use default_branch / never reopen.

Mark closed this issue

2026-08-14 05:17:08 +00:00