Documentation
Lerp’s manual. Start is install to a first promoted ticket; Concepts is the model the board is a picture of; The interface is one page per motion through the screen; Reference is the config file, the command line, and what to do when something looks stuck. SCOPE.md is published beside them, as it is written rather than rewritten.
- Overview
- What lerp is, what is in the box, and where to start.
- Install
- Platforms, the three ways to get the binary, and the prerequisites lerp cannot satisfy for you.
- Quickstart
- From `lerp init` to a first promoted ticket, in four steps.
- The board
- Tickets, queues, runners, lanes, the loop — and the claim that arbitrates between them.
- Reading the board
- The two panels, what each row says, and the main pane that opens beside them.
- Finding tickets
- Filtering, sorting, searching, and slicing to a status.
- Promoting
- Moving a ticket into the next stage — the one routing decision, and one of the board's two writes.
- Ejecting
- Taking a headless run over as your own interactive session.
- Watching a run
- The activity line, the live log tail, the raw view, and following.
- Starting past the limit
- `S` runs a queued ticket now, overriding the lane count and nothing else.
- lerp.toml
- The one file lerp reads — teams, workspace commands, runners, queues — and the stock pipeline it ships with.
- The command line
- The whole surface — `lerp`, `lerp login`, `lerp init`, `lerp version` — and the environment they read.
- Troubleshooting
- The questions a board raises — a ticket that will not start, a stage that got skipped, a run that outlived its lerp.