| ▲ | klaussilveira an hour ago |
| I encourage everyone to switch to Forgejo. We ditched GitHub and could not be happier. The experience is smoother, faster and distraction-free. Our runners are faster, our CI is smoother than ever. Transitioning was a matter of a few hours, which we took as a fun hackaton. |
|
| ▲ | sebmellen an hour ago | parent | next [-] |
| 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. |
| |
| ▲ | nrabulinski 37 minutes ago | parent [-] | | 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 | | |
| ▲ | sebmellen 27 minutes ago | parent [-] | | 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. |
|
|
|
| ▲ | ryuuseijin an hour ago | parent | prev [-] |
| Just going to leave this here - self hosted forgejo on fly.io with restic backups: https://forgejo-fly.fly.dev/forgejo-admin/forgejo-fly |
| |
