That's the plan, but it's still far away

This was always baked into basic git from the beginning if you review your code in E-Mail chains or mailing lists.

Except bluesky is funded by VC and they created their own protocol and federation design.

Codeberg is an open source repo only place, they're building in AP, they have monthly updates. So nothing like Bluesky.

But I understand the trepidation.

Codeberg is a nonprofit, that has a democratic "member" system and is fully funded through donations / member fees.

Yeah sounds like a big nothingburger to me. If you just use gitlab for private projects with basic pushing and pulling without any fancy gitlab features, switching is a matter of minutes.

Now, if you've built your entire company setup around gitlab and use everything they offer, yeah switching is gonna be a lot harder and will require more preparation. However, it's not impossible in the slightest. Even a large corporation with hundreds of developers could make a switch within 2 weeks.

Those are all part of the forge, not git.

• A git migration is easy.
• Forge migration usually requires some form of migration tool to get all the forge specific stuff (like issues, PR's and todos).

The 2 are very different things.

Those aren't git features, those are features provided by surrounding tooling, not git itself, so I didn't really consider them. I also never used them in private projects.

However, issues you can migrate easiely. I've seen tools out there that copy the issue content from github and to somewhere new. The creator of that issue is then a bot user or something, but the issue is still there and can be worked on. On github, the bot will leave a message that this issue is now handled somewhere else and closes it. Done.

Pull requests are also simple, you just merge them all. I haven't seen a lot of projects with hundreds of open pull requests that were lying there for weeks or months. Now yes, you will lose the comments and history of the pull request itself, but I don't think that's very important.

Tasks I don't know. I've never used them and don't even know what they do. If it's just a glorified kanban board with plenty of cards that say "Do X", you can just copy paste them to your new tool because there's nothing technical about them.

https://docs.codeberg.org/advanced/migrating-repos/

The problem is, I have an account on lemmy.world but switched off during a time it had major problems with downtime and broken images. When I wanted to switch to another provider, my account was not portable. I hadn’t posted or commented an overwhelming amount, but it’s still not associated with this account.

So let’s say someone creates a federated Git hosting platform and feature matches GitHub with Actions/CI etc, so there’s no reason not to switch. Let’s then say git.world starts acting up, but you can create an account on git.zip instead.

Now you have given up your commit history and any commits you make from your git.zip account is not neatly linked with your git.world account.

I’m sure this problem can be solved, but it’s vastly more important for it to be solved before federated Git hosting can replace the “security” of GitHub. We do have to consider the fact that some people point to their GitHub profile when job searching, so git contributions and commit history is more valuable than Lemmy posts.