fix: recognize breadboard's own key in closing keywords, not just #N #34

Closed
Breadway wants to merge 0 commits from fix/closing-keyword-breadboard-key into main
Owner

Closes #33

Closes #33
An agent's PR body said "Fixes ECO-17" (breadboard's key) instead of
"Fixes #17" (the underlying Forgejo issue number) — the parser only
understood the raw #N form, so no link was created and ECO-17/ECO-19
showed as two unrelated cards instead of collapsing into one.

Extended the parser to also recognize "<PROJECT_KEY>-N" closing
references (case-insensitive on the prefix), resolved via the issue's
breadboard key rather than its Forgejo number. Also nudges the MCP
create_issue tool description so agents know to reference the key
when they later open a resolving PR.

Closes #33
Breadway closed this pull request 2026-09-10 10:00:49 +08:00

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadboard!34
No description provided.