Skip to content

Migration & CI/CD

Coming to TOVIO from Git? You don't have to start over, and you don't have to migrate everything at once. These guides cover the jobs that get an existing project — its history, its workflow, and its pipelines — running on TOVIO:

  • Import from Git — bring a Git repository into TOVIO with a single command. History, local branches, and tags all carry over, and every commit's original Git hash is recorded alongside its new Change ID. This works today.
  • Your Git branching model in TOVIO — bring your workflow, not just your repo: a copy-paste setup for Git Flow, GitHub Flow, GitLab Flow, trunk-based, release trains, and forking, each as a protected_branch configuration.
  • Run a Git bridge — keep some teammates on their Git host while others work native TOVIO, with commits flowing both ways. For mixed teams during a gradual migration.
  • Run CI/CD against TOVIO — give a CI runner a scoped capability token so it builds against exactly the files it should — no broad credentials, no access to your secrets.

Which one do you need?

You want to… Start here Available
Move a repo off Git and onto TOVIO Import from Git Today
Reproduce your Git branching model (Git Flow, GitHub/GitLab Flow, trunk-based…) Branching models in TOVIO Today — lanes, land, and lane protection are built; proposals and review need a Forge
Exchange snapshots while teammates stay on Git Run a Git bridge Today — explicit bidirectional cycles, repeatable with --watch
Wire your existing pipelines to a TOVIO repo Run CI/CD against TOVIO Runner tokens today; the GitHub Actions / Spacelift wrapper is built but its Marketplace listing and publication evidence are still open

Migrating is one-way and lossless to start with

tovio git import is a read-only walk of your Git history — it never writes to your Git remote and never discards anything. You can import a repository, explore it, and throw the result away without touching the original. Start there before you commit to a bridge.

Where to go next

Last reviewed September 9, 2026

Suggest an improvement to this page Not for security reports — see disclosure