Lanes, changes & history
Navigating with lanes, and working with changes by their stable id.
- Create, list and delete lanestovio lane — the create/list/delete surface, its naming rules, and its errors.
- Switch lanes without losing uncommitted worktovio switch, the safe three-way checkout, and why you never need to stash.
- Land a lanetovio land: the target, the gates it runs first, and the flags worth knowing.
- Is my lane ready to land?health, land --dry-run and build-check — three different questions.
- Rebase a lane onto anothertovio rebase --onto, what survives it, and when it refuses.
- Create and move tagstovio tag, why a tag is set once, and what --force actually costs.
- What a change id is, and why it survives a rewritechg: identity versus blake3: commit identity, and how to trace one.
- Start a new change, parallel or drafttovio change new, its two flags, and how to describe and promote what you started.
- See everything about a changetovio change show — who, what, when, why, how.
- Work with a stack of changesStacking, what --stack actually shows, and how a stack lands.
- Fold fixups into the change that owns themtovio change absorb — what it operates on, how it attributes, and when it declines.
- Land only part of a changetovio change split, for when half your work is ready.
- Depend on a teammate's unlanded changetovio change pull, as a recorded read-only dependency.
- Abandon and restore a changeDiscarding work reversibly, and the one operation that is not reversible.
- Rewrite history safelyWhat stays stable, what a rewrite still costs, and how to reverse one.
- Port a change to another lanetovio cherry-pick, and why keeping the change id makes a backport resolve once.
- Revert a change that already landedtovio revert mints a forward inverse instead of erasing anything.
- Find the change that introduced a bugtovio bisect: a binary search over history, manual or automated.
- Explain how history got this waytovio explain — one verb, several lenses, three output formats.