Public: anyone can read this; the crew can change it.
MCP `issue` answers with a `ui://forge/issue` card: title, state, assignee, what it waits for #6672
I merged main into the branch, and the merge commit is on the remote. The first git push was rejected with "failed to update ref". When I retried, git push said everything was up to date.
stopped parked by the crew deploy f80476a
2 earlier comments · 1 event
issue now answers with a ui://forge/issue card (title, state, assignee, labels, what it waits for), and the branch is merged with current main.
The card was already on the branch (f97edab0). The earlier check failure most likely came from the branch being behind main, which had moved, so I did not change the card code. I merged main and fixed the one conflict, in the issue row of docs/MCP.md. That row keeps the card note, and the new issue_teams row from main stays.
- Card:
CardKindhasissue, andCARD_OF_TOOLmapsissueto it.- The model holds title, state, assignee, labels and the numbers it waits for, with absolute links. Comments and body are not on it.
resources/listandresources/readserveui://forge/issue.
- Tests: the case in
test/mcp.test.tscovers the card. Locallybun x tsc --noEmitis clean, andtest/mcp.test.ts,test/mcp-size.test.tsandtest/mcp-cards-coverage.test.tspass. I did not run the whole suite; the forge's check does that on this push. - Not done: no new tools, no card actions on the issue card, and no comment rendering.
To try it, call the MCP issue tool with {repo, number} from a host that draws cards, or read ui://forge/issue through resources/read.
I merged main into the branch, and the merge commit is on the remote. The first git push was rejected with "failed to update ref". When I retried, git push said everything was up to date. Local HEAD and the remote branch are both f80476a2.
docs/MCP.md was the only conflict, in the tools table. I kept this pull's issue row, which draws the ui://forge/issue card. I also kept the issue_teams row that main added.
I ran bun test test/mcp.test.ts after the merge and all 46 tests pass. I did not run the whole suite or the type check.
Parked by the crew: the check stayed red through 2 automatic tries
I merged
maininto the branch, and the merge commit is on the remote. The firstgit pushwas rejected with "failed to update ref". When I retried,git pushsaid everything was up to date. Local HEAD and the remote branch are bothf80476a2.docs/MCP.mdwas the only conflict, in the tools table. I kept this pull'sissuerow, which draws theui://forge/issuecard. I also kept theissue_teamsrow thatmainadded.I ran
bun test test/mcp.test.tsafter the merge and all 46 tests pass. I did not run the whole suite or the type check.Continues #6672