Hacker News new | ask | show | jobs
by rapnie 1328 days ago
The project is quite large and cannot be easily migrated without loss of data, due to rate limits in Github's API's. The preparation has been long going, but they are nearing a point where they move the project to a gitea server. That's vendor lock-in, right there.
1 comments
bastardoperator 1328 days ago
The Gitea repo is actually not that big. The harder part is converting issue and pull request metadata from the GitHub archive which they reference here:

https://github.com/go-gitea/gitea/pull/18165

The migration bundles all of that up so I assume the holdup is writing something that can covert that archive to something Gitea understands or can use.

link
rapnie 1328 days ago
Yes, I was referring to the entirety of the project, including all issue discussions and PR metadata.
link