I posted this on another thread. If you only want the commits, something like this works,
ssh [email protected]
mkdir project-1.git
cd project-1.git
git init —-bare
exit
git remote add alternate [email protected]:project-1.git
All you need is SSHAll 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
Re:GitHub was down again
by kenniskrag on Wednesday July 15, 2020 @02:27PM
(#23849475)
I 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.
Re:GitHub was down again
by johannes1234321 on Wednesday July 15, 2020 @02:30PM
(#23849533)
That'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.
Then set up the alternative remote on your repos.
[1]https://www.linux.com/training-tutorials/how-run-your-own-gi...