Sangam-Git

Import a repository

You don't have to abandon your history to move to Sangam-Git. You can import an existing repository — all its commits, branches, and tags — from GitHub, GitLab, Bitbucket, or any git host, in one step.

How to import

  1. Click New repository, then or import from another provider (or go straight to New → Import).
  2. Paste the source repository URL — for example https://github.com/acme/payments.git.
  3. Choose the owning organization and, optionally, a new name (if left blank, it's taken from the URL).
  4. Start the import.

Sangam-Git fetches the full history — every commit, branch, and tag — and creates the repository. Large repositories can take a few minutes; the page refreshes itself and shows progress.

Private source repositories

A public repository needs nothing more than its URL. For a private source, add credentials on the import form:

  • Username — your username on the source host (for GitLab, use oauth2).
  • Token / password — a personal access token from the source host.

These credentials are used once, for the import, and are never stored. If an import of a private repo fails, the usual cause is missing or expired credentials — retry with a fresh token.

What comes across

  • ✅ Full commit history, with original authors and dates.
  • ✅ All branches and tags.
  • ✅ The complete file tree at every commit.

What does not come across automatically are host-specific things that aren't part of Git itself — issues, pull requests, and CI config from the old host. You can set up CI fresh (and even import the old CI config), and configure branch protection and collaborators on the new repo.

We don't do push-mirror mode

Some hosts offer a "mirror" mode that continuously syncs from another provider, keeping the other host as the real home. Sangam-Git deliberately doesn't pitch that as the way to use it. A one-time import is the on-ramp; after that, Sangam-Git is where your code actually lives and where the AI-review and human-approval gates do their work. (If you want to try Sangam-Git alongside GitHub during evaluation, that's fine — just know the long-term model is to move in, not to mirror forever.)

After importing

Once the import finishes, treat it like any repository:

  • Add collaborators and set branch protection.
  • Set up CI.
  • Point your local clone at the new remote, or clone fresh from Sangam-Git.
git remote set-url origin https://sangam.example.com/acme/payments.git
git push

Migrating a whole team? We'll help you do it with you, so your history comes across intact and nothing is lost in the move. Reach out through the access request on the home page.