(c6a61b4) Resolve a board through a pointer file and a shared boards repo, and bump to 0.33.0
This commit is contained in:
@@ -202,6 +202,19 @@ resolve as a ticket. `--clear` replaces both arguments with the ticket alone.
|
||||
`worklane init` creates `.worklane/` with the five status directories and the campaigns
|
||||
directory beside them, for a repo that has no board yet.
|
||||
|
||||
**A board can be shared across machines.** `.worklane` is gitignored and not itself a git
|
||||
repo, so a clone elsewhere has no board. The shared layout keeps one boards repo cloned
|
||||
once per machine, a committed `.worklane.toml` in the project naming its board, and
|
||||
`.worklane` as a symlink into the boards directory — transparent to every command. Where
|
||||
to run `init` decides the layout: a project whose machine carries a boards config, or
|
||||
whose repo already shows a `.worklane.toml`, lands on the shared board, and everything
|
||||
else gets the ordinary local `.worklane`. A pointer whose board is missing is an unsynced
|
||||
machine and `init` refuses rather than creating a second board that would have to be
|
||||
merged by hand; `worklane init --create` is the deliberate exception for a genuinely new
|
||||
board. You only need the layout in mind when a `.worklane.toml` appears in a repo you
|
||||
are working in: it says the board is another machine's, and a missing one means pull the
|
||||
boards repo, not that the board never existed.
|
||||
|
||||
## Relating tickets
|
||||
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user