-

Thu, 20 Jan 2022 16:31:35 +0200

adnan360

adnan360@tiksi.net

Found out Gitea/Codeberg has this easy mirroring feature. Very interested to mirror some of my projects on GitLab.com to Codeberg.org.

I think I'll start with this one:
https://gitlab.com/adnan360/dicemate

#gitea #codeberg #code #repo #migration

Thu, 20 Jan 2022 17:56:31 +0200 последнее редактирование: Fri, 21 Jan 2022 08:09:08 +0200

adnan360

adnan360@tiksi.net

This is unfortunate. It seems Codeberg.org has disabled repository mirroring due to misuse. According to the article there is still a way. This is what I did:

WARNING: This is my first try at git mirroring. Please do not depend on this alone and don't try on important repositories. I'm not responsible if anything mess up.

]Create an empty repository where I want the mirror to be. So basically,

[

]After creating, I went to the organization page and then clicked "+", then New Repository...

[

]Repository Name to "pages"[

]I change "Default Branch" to "master" because my original repo had it as default[

Set up mirror on my local git repository (2 ways to do it, mentioned under a and b)a. Easier way to do it:

git push --mirror [url=https://codeberg.org/dicemate/pages.git]https://codeberg.org/dicemate/pages.git[/url]

[h1]or[/h1]

git push --mirror git@codeberg.org:dicemate/pages.git

b. More hands on way to do it:

[h1]Go to the already cloned old repo (shallow clones cause problem when pushing, details below*)[/h1]

cd /path/to/local/repo

[h1]Depending on your setup...[/h1]

[h1]HTTPS:[/h1]

git remote add codeberg [url=https://codeberg.org/dicemate/pages.git]https://codeberg.org/dicemate/pages.git[/url]

[h1]SSH:[/h1]

git remote add codeberg git@codeberg.org:dicemate/pages.git

[h1]to confirm[/h1]

git remote -v

[h1]test push[/h1]

git push --mirror codeberg -n

[h1]To push everything to new one (we get rid of -n)[/h1]

git push --mirror codeberg

Details about shallow clones. If when pushing to mirror repo it says "shallow update not allowed", you may need to run git fetch --unshallow to clone full history and then try the push command again.

So you'd have to run the usual git push command and then the above git push --mirror ... whenever you want to push to both original and mirror repo. I haven't tested this extensively and this might ruin something, but git config remote.origin.mirror true may save you from running both. It will push to every entry on git remote -v when running git push automatically.

EDIT: Changed "git push --mirror ..." part.