Repository navigation
Say that cards move --to reaches any column in the project - #910
Conversation
The move endpoint resolves column_id against every column in the card's project, on any card table, so a move to another card table in the same project is direct. The help read as though --to stayed on one card table, which steered agents to create a wormhole, move through it, and delete it. Say --to takes any column in the project, that --to-wormhole is for another project's card table, and that a wormhole is a standing shortcut rather than a per-move step.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
🟢 Approved
The help-only changes align with existing command behavior, with no unresolved findings.
No open issues 🎉
What changed in this PR
Clarifies that cards can move directly between card tables within the same project, without a wormhole. Changes affect help text and comments only.
Changes:
- Explains project-wide
--todestinations and adds a cross-table example. - Describes wormholes as reusable shortcuts rather than per-move steps.
[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or rungh pr ready --undo.
Click "Ready for review" or rungh pr readyto reengage.
| File | Description |
|---|---|
| internal/commands/cards.go | Updates move and wormhole guidance without changing runtime behavior. |
Review effort: Balanced
Agents read the
cards movehelp as saying--tostays on one card table. So to reach another card table, they create a wormhole, move the card through it, and delete it. That's never needed within a project. The move endpoint (POST /card_tables/cards/:id/moves.json) looks upcolumn_idamong every column in the card's project, on any card table (bc3Kanban::Cards::MovesController#set_column). A wormhole is needed only to reach another project.Help text only (
internal/commands/cards.go):cards move:--toaccepts any column in the card's project, including one on another card table, and the card moves there directly. A name resolves against--card-table, so a new example shows a name on another table.--to-wormholesends a card to another project's card table through a wormhole the card's table already has. The agent notes now say not to create a wormhole just for a move, and not to delete one afterward. Flag descriptions follow the same wording.cards wormholes/wormholes create: a wormhole is a standing shortcut, usually to another project, and isn't needed for a move within one.Same wording as basecamp/basecamp-mcp-server#262.
Code check:
--todoesn't restrict cross-table moves. Every path takes a column on another card table in the same project:--tocallsCards().Moveon the flat endpoint.--tolooks up the name on--card-table(any table in the project), then callsCards().Move.--to --positioncallsCardColumns().Move(POST /card_tables/:id/moves.json). bc3'sKanban::MovesControllerfinds bothsource_idandtarget_idin the bucket, not on that board.--on-hold --to <id>reads the column, then moves onto its on-hold section.So no code change is needed.
Tests:
make checkexits 0 on Linux. On macOS,golangci-lintflagsinternal/connector/driver/proctime_darwin.go(G115 and unconvert), which this PR doesn't touch, and TTY tests fail in a sandbox without a terminal. Neither is related to this change.No skill or README in this repo describes the create, move, delete routine (
rg -i wormhole skills README.mdfinds nothing).skills/basecamp-connect/subagent.mdalready moves cards on the card's own table.Summary by cubic
Updates the
cards movehelp text to clarify that--toreaches any column in the card's project, including one on another card table, so no wormhole is needed for moves within a project. Also reframes wormholes as standing shortcuts (usually for cross-project moves) rather than per-move steps, and removes the routine of creating and deleting a wormhole for each move. Help text only; no code changes.Written for commit 1938355. Summary will update on new commits.