Bring every repository home to Sailfork.
Move your whole GitHub account or organization from one page. Pull request and issue numbers carry on from GitHub's. From GitLab, Bitbucket, Azure DevOps or your own server, 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, with its teams and collaborators.
- Releases, wiki and Git LFS
- Release notes and assets, the wiki, and every LFS file the history points at.
- Rules
- Branch protection, rulesets and merge queue settings, set up as Sailfork rules.
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, ECDSA or RSA key (2048 bits or more). 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.
What comes with you
From GitHub. Other hosts move code and history; the script on this page does not carry the rest.
Comes with you
- Code, branches and tags with full history
- Commit hashes and signatures, unchanged
- Pull requests and reviews
- Issues and comments
- Labels and milestones
- Releases and the wiki
- Git LFS objects
- Collaborators and teams
- Branch protection and rulesets
- Merge queue settings
Stays behind
- Stars and followers
- GitHub Actions run history
- GitHub Apps and webhooks, which you create again on Sailfork
Not ready to leave?
Keep GitHub as the source and mirror into Sailfork, or move to Sailfork and push back to GitHub. Mirrors follow within seconds.
A push mirror sends a push to the other host about 10 seconds after it lands. A pull mirror updates by webhook from GitHub, or every 10 minutes from any server. Mirrors
Will my CI run?
Your GitHub Actions workflows run on Sailfork on machines you control. How CI works
Questions before a move
Moving a large organization? Plan it with us