Issue #39 remains open despite fix commit being on master #259

New issue

Closed

opened 2026-07-22 18:32:37 +00:00 by Mark · 0 comments

Mark commented

2026-07-22 18:32:37 +00:00

Owner

Finding from post-deploy probe (kanban task t_672a7f51)

Commit a25a277 (feat: Complete Phase 2.1 provisioning loop closure) landed on origin/master and claimed "Closes #39" alongside #38, #40, #41, #42, #43, #48, #51. All of those issues are closed — only #39 remains open.

Actual behavior: Issue #39 is still open with label triage-approved (last updated 2026-07-15), 0 comments, all acceptance checkboxes unchecked.

Expected behavior: Issue #39 should be closed, matching the other issues that were referenced in the same commit message.

Possible causes:

Forgejo auto-close did not trigger for issue #39 (cross-reference parsing issue)
The issue was reopened after the commit landed
There is a disconnect between the commit claim and the issue tracking state

Suggested action: Investigate why auto-close did not fire, close #39 manually, and ensure the Forgejo auto-close mechanism is working correctly for cross-references in commit messages.

Kanban card: t_672a7f51

**Finding from post-deploy probe (kanban task t_672a7f51)** Commit `a25a277` (feat: Complete Phase 2.1 provisioning loop closure) landed on `origin/master` and claimed "Closes #39" alongside #38, #40, #41, #42, #43, #48, #51. All of those issues are closed — only #39 remains open. **Actual behavior:** Issue #39 is still open with label `triage-approved` (last updated 2026-07-15), 0 comments, all acceptance checkboxes unchecked. **Expected behavior:** Issue #39 should be closed, matching the other issues that were referenced in the same commit message. **Possible causes:** 1. Forgejo auto-close did not trigger for issue #39 (cross-reference parsing issue) 2. The issue was reopened after the commit landed 3. There is a disconnect between the commit claim and the issue tracking state **Suggested action:** Investigate why auto-close did not fire, close #39 manually, and ensure the Forgejo auto-close mechanism is working correctly for cross-references in commit messages. **Kanban card:** t_672a7f51