I am seriously impressed by #Forgejo's (the software powering #Codeberg and other GitHub alternatives) migration tool.

Git history, issues, PRs, wiki data; all migrated perfectly from GitHub.

You can link your GitHub account afterwards, and all migrated things move over to your user - so you can edit things like comments you originally wrote on GitHub. It's like the migration never happened.

It even migrates tiny details like comment reactions.

And because the account linking is lazy, users that haven't yet joined Codeberg aren't losing out: the moment they join and connect their account, they suddenly own everything they did on the old repository.

This is wizard shit. I'm a bit blown away at how flawless and easy the process was.

@jsbarretto

<blockquote>moment they join and connect their account, they suddenly own everything they did on the old repository.</blockquote>

Wow this in particular is awesome.

I haven't needed to use the migration tool personally because all my repos are single-contributor but its great that it exists

@spacebuffer Yeah, I did not expect this to work at all. I would have been satisfied if it was just tied to a null user or something and the issues became append-only. But it does work, and it's so wonderful.

The PR migration is really clever too. Obviously the user that opened the PR doesn't have an account yet so it looks like the source branch gets attached to the target repository, but is hidden and isolated somehow (unless you explicitly click through to it), which is pretty much the best solution I can realistically imagine.

@jsbarretto @Codeberg I hope they will consider adding my bitbucket importer https://codeberg.org/magnusmanske/bitbucket_issues2forgejo
(shameless plug)
bitbucket_issues2forgejo

Import a BitBucket issue export file (db-2.0.json) into a Codeberg/FORGEJO instance.

Codeberg.org
@jsbarretto
I use my own Forgejo instance. I love it like anything.