Bring every repository home to Sailfork.
From GitHub, GitLab, Bitbucket, Azure DevOps or your own server. Authorize GitHub and we move it for you. From anywhere else, one script moves it and checks nothing was left behind.
- github.com/acme-pay/api sailfork.com/acme-pay/api matches
- github.com/acme-pay/web sailfork.com/acme-pay/web matches
- gitlab.com/acme-pay/platform/billing sailfork.com/acme-pay/billing matches
- bitbucket.org/acme-pay/ios sailfork.com/acme-pay/ios matches
- dev.azure.com/acme-pay/payments/_git/ledger sailfork.com/acme-pay/ledger matches
- git.acme-pay.dev/tools/deploy sailfork.com/acme-pay/deploy matches
Where you are coming from
Code moves from anywhere git runs. How much else comes with it depends on the host.
We move it for you
Authorize GitHub, pick repositories or whole organizations, and we copy everything over. Nothing changes on GitHub.
- Code with its whole history
- Every branch, tag and commit, with authors, dates and signatures as they were.
- Issues and pull requests
- With their comments and reviews, so the reasons behind the code come along.
- Private repositories
- Moved the same way, and private on Sailfork.
- Organizations
- Pick an organization and every repository in it comes over together.
Moving from GitHub
Three steps, and only the first two are yours.
- 1
Authorize GitHub
Approve access for your account and the organizations you want to bring. New to Sailfork? This creates your account too.
- 2
Pick what moves
Every repository you can see on GitHub is listed by owner. Pick a few, or a whole organization at once.
- 3
We move it
We copy everything over and email you as each repository is ready on Sailfork. Nothing changes on GitHub.
Your team, after the move
A few minutes each, mostly on day one.
- Your clones
- Point each one at Sailfork with one command:
git remote set-url origin https://sailfork.com/owner/repository.git - Signing in
- Your team signs in with GitHub, so there are no new passwords to hand out.
- SSH keys
- Add an ed25519 or ECDSA key. RSA and DSA keys are refused, so if yours is older, make a new one:
ssh-keygen -t ed25519 - Branch protection
- Branch rules require a pull request and a number of approvals before anything lands on a protected branch.
Move it yourself
From GitLab, Bitbucket, Azure DevOps or your own server, paste the repositories and run the script we write for you. It copies every branch and tag and checks nothing was left behind. Create the empty repositories on Sailfork first.
One per line, the way you would pass it to git clone.
The script
Paste at least one repository above.
Questions before a move
Moving a large organization? Plan it with us