CLITodo
Todo
12 `hanzo` commands for Todo, each calling one operation on api.hanzo.ai.
Package todo is Hanzo Todo: boards, the work items on them, and the filters that make a board.
12 commands · API reference →
| Command | Calls | What it does |
|---|---|---|
hanzo todo board | GET /v1/todo/board | Returns a board's issues — work items with their column, priority, assignee, labels and schedule. |
hanzo todo issues | GET /v1/todo/issues | Answers across every project in the org. |
hanzo todo projects issues claim <key> 1 | POST /v1/todo/projects/{key}/issues/{num}/claim | Takes an issue: it becomes yours and it moves to in_progress. |
hanzo todo projects issues get <key> 1 | GET /v1/todo/projects/{key}/issues/{num} | Returns ONE work item in full — its description included. |
hanzo todo projects issues update <key> 1 | PATCH /v1/todo/projects/{key}/issues/{num} | Edits a work item — rename it, rewrite it, move it to another column, or re-prioritise it. |
hanzo todo projects issues list <key> | GET /v1/todo/projects/{key}/issues | Returns a board's issues — work items with their column, priority, assignee, labels and schedule. |
hanzo todo projects issues create <key> | POST /v1/todo/projects/{key}/issues | Opens a work item on the board — an issue on that repository on the deployment's forge, filed as YOU. |
hanzo todo projects get <key> | GET /v1/todo/projects/{key} | Returns one board of your org by its key — the repository name. |
hanzo todo projects update <key> | PATCH /v1/todo/projects/{key} | Refused — a board is a repository on the forge |
hanzo todo projects rm <key> | DELETE /v1/todo/projects/{key} | Refused — a board is a repository on the forge |
hanzo todo projects list | GET /v1/todo/projects | Returns the boards of your org — the places your work actually is. |
hanzo todo projects create | POST /v1/todo/projects | Refused — a board is a repository on the forge |
How is this guide?