Well, not officially supported anyway…

Sounds like not lazy at all. If anything more work depending on the number of repos!

That sounds pretty nice. Did it also handle issues and comments and stuff?

I don’t understand. How would that help switching from a Gitea 1.25.x instance?

The best time to do was before the hard fork. The second best time was was, well, now. Also, I am the user(s) of this former Gitea instance, just in terms of who owns the repos on it. And like I said above, I didn’t want to lose all of the data that the built-in migration feature wouldn’t migrate.

I think you underestimate how much of step up it would be for the neighbor’s kid to do my taxes.

Personally, I think it’s great to have multiple options in this space. I think we can all agree that self-hosting (or using Forgejo/Gitea on a smaller platform, e.g. Codeberg) is preferable to centralizing absolutely everything on Microsoft GitHub.

That would be ideal if it worked, yeah. But personally I wouldn’t want to manually recreate the bits that it didn’t support migrating. I realize everyone’s instance and situation is different.

Lol that’s a good idea… I hate doing taxes!

I haven’t either. 😄 But I’m just taking Forgejo’s docs on this at their word.