When something goes wrong

Find the message you got below (press `/` and type a few of its words), or the situation you're in. ## Messages from zev ### "Not a zev repository" You ran a command outside a project. `cd` into the project folder (the one with the hidden `.zev` folder), or run `zev init` to make the current folder a project. ### "Nothing to commit (staging area is empty)" You haven't staged anything. Stage your changes first: ```bash zev add . zev commit -m "message" ``` ### "Nothing new to add: no changes since the last commit" The files you named are exactly as they were in the last commit, so there's nothing to stage. Check `zev status` to see what really changed. ### "'file' doesn't exist, and zev doesn't track it" The path is wrong (check spelling and the folder you're in), or the file was never committed, so there's nothing to stage. ### "'file' is ignored (it matches a pattern in .zevignore)" A line in `.zevignore` matches this file. Remove or change that line if the file should be tracked. ### "Not switching to 'branch': you have local changes" Switching would overwrite changes you haven't committed, and zev never does that silently. Pick one: ```bash zev commit -m "work in progress" # keep them, on this branch zev stash # keep them, aside (zev stash pop later) zev checkout --force branch # throw them away ``` ### "Working files NOT updated" `zev pull` got the new commits, but didn't change your files, because one you changed would have been overwritten. Nothing is lost. Commit or stash your changes, then: ```bash zev checkout <your-branch> ``` ### "Can't bring 'branch' in automatically: … changed the same lines" A merge conflict: both branches changed the same lines. Run `zev merge <branch> --resolve` and follow [When both changed the same lines](/docs/en/branches#when-both-changed-the-same-lines). ### "has changes that aren't committed. Nothing was removed." `zev rm` refuses to delete a file with uncommitted changes. Commit them first, use `zev rm --cached` to stop tracking but keep the file, or `zev rm --force` to delete it anyway. ### "Not applying stash: 'file' has changes of its own" You changed a file after stashing, and the stash would overwrite it. Commit or stash those newer changes, then `zev stash pop` again. ### "No remote named 'origin'" The project isn't connected to Zaryn yet. Either create it there: ```bash zev new ``` or connect it to an existing repository: ```bash zev remote add origin owner/project ``` ### "Challenge request failed" when signing in This project's identity has no account on the server yet. Create one with `--register` and `--email`, or, if you made your account on the website, sign in with `zev login zaryn.xyz --device`. ### "Could not reach …" zev couldn't connect to the server. Check the address (for Zaryn, `zaryn.xyz` is enough), your internet connection, and any proxy or firewall. ### HTTP 401 or "unauthorized" You aren't signed in, or your token was revoked or expired. Run `zev whoami` to check, and `zev login` again. ### HTTP 403 or "forbidden" You're signed in, but your account can't do this here: for example, pushing to someone else's repository. Ask the owner to add you, or [fork it](/docs/en/how-do-i#contribute-to-a-project-i-cant-push-to). ### HTTP 402 The action needs Premium or more credits (private networks, some advanced tools). See [Billing and credits](/docs/en/billing-and-credits). ### HTTP 413, or "quota" The push is bigger than your plan allows (repository size or file size). Remove big generated files from the commit, ignore them, or upgrade. ### "Unknown command" A typo, or a git command zev names differently. zev suggests the closest command. Some common ones: | git | zev | |---|---| | `git reset <file>` | `zev restore --staged <file>` | | `git checkout -- <file>` | `zev restore <file>` | | `git switch -c <branch>` | `zev switch -c <branch>` (or `zev checkout -b`) | | `git fetch` + `git merge` | `zev pull` | | `git mv a b` | rename the file, then `zev add a b` | ## Situations ### I committed something I shouldn't have If you haven't pushed: fix the files and make another commit (zev doesn't rewrite commits). If it was a secret, such as a password or key, treat it as leaked once it's in history: change the secret, then stop tracking the file: ```bash zev rm --cached .env echo ".env" >> .zevignore zev add .zevignore zev commit -m "Stop tracking .env" ``` ### My push contains a huge file by mistake Stop tracking it, ignore it, and commit: ```bash zev rm --cached data/big.csv echo "data/big.csv" >> .zevignore zev add .zevignore zev commit -m "Don't track the big CSV" ``` For data and model files you do want to keep, zev handles large files well: only the changed parts of a file are sent on each push. ### zev printed a long list of lines with "error:" and file names That's a crash report. Please tell us: open an issue on Zaryn with the command you ran and the first lines of the output, or write to us from the Contact page. ### zev is old, or a command is missing ```bash zev --version zev self update ``` ### Cloning or pulling is slow zev 0.4 and later download in batches: a few requests instead of one per file. Older versions fetch every file on its own, which is slow on a long or filtered connection. Check with `zev --version` and update with `zev self update`. If it's still slow, the connection may be throttled: see [the proxy](/docs/en/proxy). ### I still can't figure it out - `zev help <command>` explains any command. - [How do I…?](/docs/en/how-do-i) covers the common tasks. - Ask on Zaryn: the Contact page reaches the team.