Everyday version control
The commands you run twenty times a day.
- See what is going on: tovio statusReading lane, change and working-copy state, and the two flags status actually defines.
- Commit your worktovio commit, its full flag set, and why there is nothing to stage first.
- Fix the last commit without breaking its identitycommit --amend keeps the stable change id.
- Read history with tovio logThe default topology graph, and every flag that narrows or reshapes it.
- See why a change was madelog --why, what an attested rationale is, and which surfaces actually write one.
- Filter history by human, agent, task or dateThe queries that matter once agents are committing.
- Diff your working copytovio diff, against the last commit — and the diffs that are not it.
- Find who changed a line and whytovio blame, with rationale and run record.
- Undo almost anythingtovio undo and redo, over the local op-log.
- Throw away edits to one filetovio restore, the one command that can lose work.
- Read a file at any revisiontovio cat, including one side of a conflict.
- Rename or move a tracked filetovio mv, and why the move is recorded rather than guessed.
- Ignore files with .tovioignoreKeeping build output and local junk out of your changes — and what is already excluded.
- Get machine-readable output--json, --quiet, exit codes, and the contracts scripts can rely on.
- Search your files with tovio grepSearching the working copy or any revision, including protected files you hold a key for.
- Find the change that introduced a lineThe pickaxe: tovio log -S and -G.
- Check and compact the repository: fsck and gcEveryday repository maintenance, and what each command will and will not touch.
- Set your preferences with tovio configTurning off hints, celebration lines and git-compat notes, and the keys worth knowing.