A guided path from your first repository to signed, provable history: what code hosting is, how zev and Zaryn work, the everyday loop, branches and pull requests, finding and undoing things, and the advanced features. Pictures first, every step explained.
What zev and Zaryn are, what they are made of, and what they can do.
What zev does that Git doesn't, what stays the same, and every everyday Git command next to its zev form.
Move a Git repository to zev in three commands. Preview what comes over, import it in place or straight from its address, and get proof that every commit and file matches Git. Real examples for an open source project, a company repository with LFS, submodules and hooks, and a team that switches gradually.
Short answers to the things people most often need to do. Find yours in the list on the right, or press / to search.
zev undo takes back the last thing you did, whether a commit, merge, rebase, deleted branch or add, without ever overwriting work that isn't saved anywhere. zev recover brings back edits a command threw away. zev op log shows every change.
Work on new ideas without touching your main code, then bring them back in. Includes fixing merge conflicts, step by step.
When two branches changed the same lines. zev shows each conflict with your side, the base and theirs, settles them with one command instead of an editor, and lets you commit them now and resolve later. Every step is data for scripts and AI agents.
Split big work into a chain of small branches, each on the one below. zev stack restacks them together after an edit, pushes them as one pull request each, and cleans up as they merge.
Another repository inside yours, pinned to a commit: a shared UI kit, a vendored library, a dataset. zev fetches and updates it on clone, checkout and pull by itself, keeps the pin in a file you review, and never throws away work done inside it. What Git's submodules should have been.
zev signs every new commit on your computer with the repository's Ed25519 key. Add the key to your account once and Zaryn shows those commits as Verified, with your name.
Every zev command, with the ones you'll use every day first. Each entry says what it does, how to type it, and shows examples.
Issues, pull requests, forks and reviews, all from the terminal.
Use zev from scripts, CI, servers and AI agents: tokens, JSON output and the MCP server.
zev sdiff compares Zig code by function (added, removed, signature or body changed) from the compiler's own parser, not lines of text.
zev's messages, what they mean, and what to do. Search for the words of the message you got.