Move your repositories from GitHub, GitLab or Bitbucket
Bringing a project over takes a minute and keeps everything: every branch, every tag, the full history. Use the panel's import when the old host is reachable, or push from your own copy when it isn't — for example when an account has been suspended.
1
Import in the panel
On the Git page, paste the repository's HTTPS address (https://github.com/you/project) under Import from GitHub or GitLab and choose Import. Public repositories need nothing else.
2
Private repositories
Add an access token from the old host with read access to that repository — on GitHub a fine-grained token with Contents: Read, on GitLab a token with read_repository. The token is used for this one copy and never stored. With a GitHub or GitLab token, issues, pull requests, labels and releases come across too.
3
Or push from your computer
Create an empty repository on the Git page, then push every branch and tag from your local copy with the commands below. This works for any host, and even when the old one is gone.
4
Switch your apps
On each app's Overview, use Move to Belov Git, pick the repository and branch, and hit Deploy now. Read access is granted for you, and from then on every push deploys.
5
Tell your team
Teammates run the two remote commands below in their own copies (or clone fresh). Their access is already there — it follows their role in your Belov Cloud team.
Push an existing local copy — every branch and tag
cd my-project
git fetch --all # if the old host is still reachable
git remote rename origin old
git remote add origin git@git.belov.cloud:your-org/my-project.git
git push origin --all
git push origin --tags
CI workflows
Belov Git keeps your .github/workflows files but doesn't run GitHub Actions. Apps hosted with us don't need it to deploy: the build runs on every push, isolated and health-checked, with one-click rollback.
New to Belov Git? Start with signing in and adding your SSH key.
