(c6a61b4) Resolve a board through a pointer file and a shared boards repo, and bump to 0.33.0

This commit is contained in:
Ansho Rei
2026-09-01 17:41:05 +02:00
parent 3892afe819
commit f877e6dbf2
13 changed files with 1200 additions and 32 deletions
+30 -1
View File
@@ -6,7 +6,7 @@ Worklane is a local Kanban flow for agentic software development.
| Command | Description |
|---------|-------------|
| `worklane` or `worklane tui [path...]` | Opens the board: one column per status, redrawn when the tree changes. Read only. Opens with done and discarded hidden, their counts in the footer; `d` rotates hide both, show done, show both, and back around. Arrows or `hjkl` to move, `enter` for detail, `pgup`/`pgdn` to scroll an open ticket or the campaign frame, whichever the selection is on, with a page indicator on its border while there is more of it than fits, `/` to jump to the first ticket whose id or title matches, `y` to copy the selected ticket's short id to the clipboard, `c` to pick a campaign and filter the columns to its members, `q` to close whatever is open and then to quit. A card carries its campaign beside its tags, marked `~` and bold, and a comment count in its bottom right corner, the number then `❞` in cyan, before the criteria count and absent entirely when nobody has commented; while one is selected a frame above the columns names it, shows three rows of its description and says how far it has got, and `q` on its border gives the whole board back; up from the top card of a column moves the selection to that frame, where the scroll keys page through the description, `enter` gives it half the board and takes the rows back again, and down returns to the column it came from, leaving the frame at whatever height it was. Each path opens the first `.worklane` at or above it, the working directory by default. Several paths are monitored together, as a tab per project plus an `all` tab that merges them, with `tab` and `shift+tab` between them |
| `worklane init` | Creates `.worklane/` with backlog, committed, reviewing, done, discarded directories |
| `worklane init` | Creates `.worklane/` with backlog, committed, reviewing, done, discarded directories. On a machine with a boards config, or in a project that already carries a `.worklane.toml`, it puts the project on the shared layout instead: the board lives in a boards directory under the machine's data dir and `.worklane` becomes a symlink into it. `--create` makes a new board under a pointer that names a missing one, the only way to do so. See Shared Boards |
| `worklane add` | Creates a ticket in backlog with `--title`, `--description`, `--acceptance`, `--plan`, `--tags`, `--due`, `--owner`, `--priority` flags. `--due` takes `YYYY-MM-DD` and refuses anything else at parse time |
| `worklane ls [status]` | Lists tickets, each column in its own order: the backlog by due date, soonest first, then priority then title, with an undated ticket below every dated one; committed and reviewing by when the ticket entered them, oldest first; done and discarded newest first. Optional positional status, and `--priority <1-5>`, `--tag <tag>` and `--campaign <campaign>`, which compose in any combination. `--tag` matches a whole value of the comma-separated Tags field, case sensitively, so `--tag bug` does not list a ticket tagged `bugfix` or one tagged `Bug`. `--ids` prints one ticket per line as its short id, a tab and its title, unstyled, done included, for a script or a completion |
| `worklane show <id>` | Shows ticket by UUID prefix (4+ chars), title substring, or filename substring. A campaign is addressed the same way, plus its exact codename, which wins over all three. Ends with the ticket's history: every comment on it and every change to its status, owner or tags, oldest first, each naming who made it |
@@ -70,6 +70,35 @@ installed binary to be current**: an older one without `--ids` completes nothing
`tui` is the one command whose argument is a path, so it is the one place fish still offers
directories.
## Shared Boards
A board exists on exactly one machine: `.worklane` is gitignored and not itself a git repo, so cloning
a project elsewhere gives you no board. The shared layout answers that: one boards repo is cloned once
per machine to `~/.local/share/worklane/boards`, holding a directory per board named `uuid_slug` after
the ticket filename convention; the project commits a `.worklane.toml` naming its board by uuid; and
`.worklane` in the project becomes a symlink into it. The symlink is what keeps every other tool
working — with no `.worklane` directory, `cat .worklane/backlog/*.md` stops.
The boards repo url lives in the machine config at `~/.config/worklane/config.toml`, so a client repo
never carries a hostname. The pointer names the board, not the server.
`init` decides where a project is on by the following table, and `--create` is the only way to make a
board under a pointer that names a missing one:
| pointer | boards repo | `.worklane` | outcome |
|---|---|---|---|
| none | irrelevant | none | local `.worklane`, as always |
| none | on this machine (config) | none | create the board, write the pointer, symlink |
| present | board found | none | symlink, and nothing is created |
| present | board absent | none | refuse: an unsynced machine, fetch and look again |
| present | repo not cloned | any | refuse, saying the repo is not cloned here |
| present | board found | link to it | no change, nothing written |
| present | board found | link to another | refuse rather than repoint |
| present | board found | dangling link | refuse rather than replace |
| present | board found | real directory | refuse, and name the adopt path |
Resolution is a uuid prefix match, so renaming a board's slug breaks no committed pointer.
## Exit codes
| Code | Meaning |
|------|---------|