In the end, we opted for a simple strategy, sidestepping GitHub’s aggressive vendor lock-in: leave the existing issues open and unmigrated, but start counting issues at 30000 on Codeberg so that all issue numbers remain unambiguous. Let us please consider the GitHub issues that remain open as metaphorically “copy-on-write”.
Do you know anything about the referenced vendor lock-in?
Basically all the stuff that is build by GitHub and not part of git. Like the pull request discussion boards that is not stored in the git repository. They can’t transfer that out of GitHub to another git host.
The original blog post is rather frank and to the point. Wish the engineering leadership I worked with communicated this well.
Do you know anything about the referenced vendor lock-in?
Basically all the stuff that is build by GitHub and not part of git. Like the pull request discussion boards that is not stored in the git repository. They can’t transfer that out of GitHub to another git host.
Aha, shrewd…
Thank you
Im pretty sure that is possible on forgejo if given a specific github token. Or is it a scale problem?
You get rate limited to hell
It’s just that all your shit and users are there, like issue tracking in this case.
The fucking lunacy of the AI bros he lists as examples…