How complex is the CI migration? We’re heavily dependent on GitHub Actions and the full GitHub ecosystem by extension, but by the same token these frequent outages are destroying us.
Forgejo actions are by design compatible with GHA. Obviously if you still depend on github to get reusable actions you’re just as dependent on GitHub being up as ever, but you can very easily migrate or mirror GitHub repositories to your forgejo instance and in most cases migrating the CI requires close to no changes. Not all features are supported, but I haven’t had the need to make any changes to my actions, and they’re continuously making improvements so compatibility only goes up
How about ticketing? We use Linear and their integration with GitHub is pretty buttery. Willing to give it up for better service stability, but wondering if Forgejo offers any kind of native ticketing integrations. I know GitLab does, but I'm not massively impressed with GitLab either.
I know at least part of the API is fully compatible with GitHub so chances are as long as you can specify custom URL base and auth token, there’s a chance linear and other integrations will “just work” too. E.g. I had migrated a custom action which interacted with the PR it was run inside of using the GitHub JS client, and I didn’t have to change a line.
The only possible good Microsoft could do, in order to salvage their relationship with id software fans, would be to honor Carmack's legacy and release the RAGE engine (id tech 5) as open source. A lot of it was already released in the Doom 3 BFG release, might as well do the whole thing.
reply