Closing-keyword parser missed breadboard's own key format #33

Closed
opened 2026-09-05 10:18:09 +08:00 by Breadway · 0 comments
Owner

Real failure: an agent opened a PR body with "Fixes ECO-17" (breadboard's own key) instead of "Fixes #17" (the 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. Extended the parser to also recognize "<PROJECT_KEY>-N" closing references (case-insensitive), resolved via the issue's breadboard key instead of its Forgejo number. Also added a nudge to the MCP create_issue tool description so future agents know to reference the key when they later open a resolving PR.

Real failure: an agent opened a PR body with "Fixes ECO-17" (breadboard's own key) instead of "Fixes #17" (the 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. Extended the parser to also recognize "<PROJECT_KEY>-N" closing references (case-insensitive), resolved via the issue's breadboard key instead of its Forgejo number. Also added a nudge to the MCP create_issue tool description so future agents know to reference the key when they later open a resolving PR.
Sign in to join this conversation.
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#33
No description provided.