Words you'll see

### Branch A named line of commits. Repositories start with `main`. You make branches to work on something separately and [merge](#merge) it back later. See [Branches and merging](/docs/en/branches). ### CI Continuous integration: a server that builds and tests your project automatically whenever you push. Turn it on with `zev ci enable`. ### CID Content identifier: an ID computed from an object's content (its [hash](#hash)), in the format IPFS uses. The same content always has the same CID. ### Clone A full copy of a repository, history included, on your computer. Made with `zev clone`. ### Commit A saved version of your project: the staged changes, plus your name, the time and a message. Each commit points to the one before it, which is what makes the [history](#history). Made with `zev commit`. ### Conflict When two branches changed the same lines of a file, so zev can't combine them by itself. You decide what the lines should be. See [When both changed the same lines](/docs/en/branches#when-both-changed-the-same-lines). ### Diff The difference between two versions of a file: lines added (`+`) and removed (`-`). Shown by `zev diff`. ### Fork Your own copy of someone else's repository on Zaryn. You change it freely, and can send changes back with a [pull request](#pull-request). Made with `zev fork-repo`. ### Hash A short fingerprint computed from data. Change one byte and the hash changes completely. zev identifies every file, folder and commit by its hash (BLAKE3), which is why commit IDs look like `5f7f5e22…`. ### HEAD The commit you're on now: the newest commit of your current branch. `HEAD~1` is the one before it, `HEAD~2` the one before that. ### History All the commits of a branch, newest to oldest. See it with `zev log`. ### Ignore Telling zev not to track some files (build output, logs, secrets) by listing them in a `.zevignore` file. ### Issue A bug report, idea or task, attached to a repository on Zaryn. `zev issue` opens one. ### Merge Bringing the commits of one branch into another. `zev merge <branch>`. ### Origin The usual name of the remote your project came from or was published to. `zev new` and `zev clone` set it up, and `zev push`/`zev pull` use it when you don't name another. ### Pull Getting new commits from a remote and updating your files. `zev pull`. ### Pull request A request to merge one branch into another, usually with a review first. Opened with `zev pr` or on Zaryn's website. ### Push Sending your commits to a remote, such as Zaryn. `zev push`. ### Remote A named address of another copy of the repository, such as `origin` on Zaryn. `zev remote` lists them. ### Repository A project whose history zev keeps: your files plus the `.zev` folder. Often shortened to *repo*. ### Restore Putting a file back the way it was in the last commit (throwing away your edits), or taking it out of the staging area with `--staged`. `zev restore`. ### Stage, staging area Picking changes for the next commit. The staging area is the list of changes you've picked. `zev add` stages, `zev restore --staged` unstages. ### Stash A place to put uncommitted changes aside for a moment, leaving a clean folder. `zev stash`, then `zev stash pop` to bring them back. ### Tag A fixed name for one commit, usually a release such as `v1.0`. `zev tag`. ### Token A long secret that lets a program act on your Zaryn account, like a password just for it. `zev login` makes and saves one for you. You can see and revoke tokens in Settings → AI agents and tokens. ### Tracked file A file zev keeps the history of: it's in a commit or staged. New files are *untracked* until you `zev add` them. ### Working folder Your project's files as they are on disk right now, including changes you haven't staged or committed. ### Zaryn The website at [zaryn.xyz](https://zaryn.xyz) where repositories live online, with issues, pull requests, CI and more. zev is the tool on your computer; Zaryn is the place you share to. ### zev The command-line tool: version control for code, data and models. ### .zevignore The file that lists what zev should ignore. See [Ignore files](/docs/en/how-do-i#ignore-files-build-output-logs-secrets).