fix: close implements tracker gap and clarify closing keywords (#110) #116
Reference in New Issue
Block a user
Delete Branch "fix/issue-110-implements-tracker-gap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recognize implement, implements, and implemented keywords to release status:in-progress during PR cleanup. Remove refs/ref keywords to avoid over-releasing claims on merely referenced issues. Update runbooks and templates to clarify Gitea issue-closing behavior. Closes #110.
0bbbca4223to472e6850feApprove. Reviewed pinned head
472e685from a detached review worktree.Scope matches #110 exactly:
extract_linked_issue_numbersregex now recognizesimplement/implements/implemented #Nforstatus:in-progressrelease AND dropsrefs?/refso merely-referenced issues are no longer over-released — both directions of the tracker gap. Regex alternation verified correct for the "implemented" suffix case. Docs/templates clarify that Gitea only auto-closes on true closing keywords. New test covers positives, the refs-must-NOT-match negatives, and the branch-name fallback.Validation at
472e685:py_compile×4 OK ·bash -n scripts/clear-provenanceOK ·pytest tests/ -q358 passed, 6 skipped (357 base + new hygiene test) ·git diff --checkclean · secret sweep clean. Mergeable per Gitea (earlier conflict resolved after #114/#115 landed).Merging next via the gated tool with pinned head + expected file set.
Review Metadata: