A new home for your repositories.
This guide walks through moving a repository onto Isurus — whether it lives in Git, Mercurial, or Fossil today. The process preserves your full commit history and doesn’t require workflow changes.
From Git
To keep it on Git, push directly: create an empty repository on your Isurus tenant, add it as a remote, and git push. A Jujutsu / jj repository works too — it’s a Git repo server-side. To convert to Mercurial, use the built-in importer: paste the Git URL and Isurus converts it on your tenant, preserving full history and mapping branches (main/master → default). Import one branch or all; snapshot mode starts clean while keeping old history as a log.
From Mercurial
Clone your existing repository with hg clone — Mercurial’s native protocol preserves full history. Then create an empty repository on your Isurus instance, add it as a remote, and hg push. Your repository is live on Isurus.
From Fossil
Create a repository on your Isurus instance and sync your existing Fossil repository to it over Fossil’s native HTTP protocol. Your check-in history comes across intact. The in-app help has detailed walkthroughs for each VCS, including the built-in Git importer and command equivalents.
Set up CI
Create a .isurus-ci.yml at the repository root. Pipelines run on Docker or Incus agents that you provision and register with your instance. A full YAML reference is in the CI/CD help doc.
Point your integrations at the new URL
Outbound webhooks, remote CI triggers, and other integrations just need to be pointed at your new Isurus URL. The payload format is a standard HTTP POST with a JSON body, so existing integrations adapt with minimal change.
Coming from a different forge or VCS?
Tell us what you’re on — we’re expanding conversion coverage, and we reply personally.