Coming from Git
Translating Git habits, importing history, and keeping GitHub while you evaluate.
- The Git to TOVIO cheat sheetCommand for command, checked against the shipped CLI — including the ones that look familiar and are not.
- Import a Git repositoryBringing history, branches, tags and authors across with tovio git import.
- What import carries over, and what it does notSet expectations before the import rather than after it.
- Where did the staging area go?There is no git add, and why that turns out to be fine.
- Branches are called lanesThe rename, and the more important thing underneath it.
- Why you never see "diverged history"The error TOVIO removed rather than reworded — and the one place it comes back.
- What replaces git stash, reset and reflogThree habits with three different answers.
- Keep using GitHub while you evaluateThe bidirectional bridge, its namespaces, and what it refuses to do.
- Let plain Git clients talk to a ForgeThe GitHub-compatible smart-HTTP surface: clone, push, and refs/for.
- Export TOVIO history back to GitThe one-shot export, and exactly what is lossy about it.
- My git push or git add "did nothing"The compat aliases, and why one of them is a deliberate no-op.
- Move a team off Git without a flag dayRunning both, and how to cut over.
- Your dotfiles are not tracked by defaultThe single biggest difference between .tovioignore and .gitignore.
- Open a proposal by pushing to refs/forThe Gerrit-style magic ref, for teams still using plain git.
- Git commands with no TOVIO equivalentThe honest gaps, and what to do instead of each.
- Bringing a Git LFS repository acrossWhy the pointers arrive instead of the bytes, and how to fix it before importing.
- Check an import before you trust itTen minutes of verification that prevents a bad migration.