4 ms·
What's the easiest way to duplicate all your Github repositories, with history, somewhere else? Ideally, I'd like to have two synchronized repositories, for no
by Animats 6y ago
What's the easiest way to duplicate all your Github repositories, with history, somewhere else?
Ideally, I'd like to have two synchronized repositories, for no single point of failure, organizational or otherwise.
- ddevault 6y agogit remote set-url --add origin git@somewhere.else:my-project This will make it so that every time you push to "origin", it'll push twice, to two places. You can repeat this to add a third or more.
- jankassens 6y agoYou could probably use GitHub actions to push any commits and branches to GitLab or anywhere else.
- throwaway744678 6y agogit add remote NAME URL git push NAME It will not transfer GitHub specific content (issues, PE, wiki, etc.), though.
- vorpalhex 6y agoGitlab has a feature set for this that's automated but it may be rolled under a paid plan if you want it to be bidirectional. Building this in git itself is not hard at all, and there's likely a script or plugin for gogs or gitea.
- monokh 6y agoRun git on a personal server[1]? It's not as complicated as you might think. Probably much more usable to setup gitlab. Then set up the alternative remote on your repos. [1]https://www.linux.com/training-tutorials/how-run-your-own-git-server/ https://www.linux.com/training-tutorials/how-run-your-own-gi...
- rovr138 6y agoI posted this on another thread. If you only want the commits, something like this works, ssh user@git.example.com mkdir project-1.git cd project-1.git git init —-bare exit git remote add alternate user@git.example.com:project-1.git All you need is SSH
- kenniskrag 6y agoI use it also that way. Gitlab does the same if you use ssh. They provide hooks on init so that gitlab knows if something happens.
- judge2020 6y agoAll you need to get all commits and all tags/branches: git clone --mirror https://github.com/you/repo Push those to another server: git remote add new https://gitlab.com/you/repo git push --mirror new
- johannes1234321 6y agoThat's fine for your code repository. However git has more: - Bug tickets - PR - Wiki - many projects use their githubpages as primary homepage - newly GitHub actions And then: Often collaborators are only known and identified by their GitHub handle. Running an own server requires some mechanism to identify them again and creating a way to handle their access credentials (ssh key etc.) Moving a mildly successful project isn't easy. Good if more people plan for that eventuality, even if they stay on GH for the time being.
- kenniskrag 6y agogit clone ... which you already have git remote add originFoo URL git push --all originFoo There are other flags like mirror but never used them. Source: https://git-scm.com/docs/git-push https://git-scm.com/docs/git-push
- ebg13 6y agoOther answers talking about using git features are assuming that you don't care about Wiki/PRs/Issues/Labels/etc that are GitHub metadata not part of your repo history. But GitLab does have feature support for extensive importing and mirroring. https://docs.gitlab.com/ee/user/project/import/github.html https://docs.gitlab.com/ee/user/project/import/github.html (Import your project from GitHub to GitLab) has a section on project mirroring.