Since its inception, Forgejo (a self-hosted git forge, like GitHub) has been a soft fork of Gitea. Upgrading to it was - and for the time being, remains to be - as simple as changing the URL from which the release is downloaded. Over time, the way Forgejo is governed and developed evolved. To be able to provide stable, secure, reliable releases, Forgejo requires a reasonable effort made at writing tests for each change that goes into the code. This has worked out remarkably well, as it caught...| forgejo.org
Ever since the announcement of the soft-fork of Gitea and the reasoning behind it, I wanted to move to Forgejo. Finally, I made it happen. In this article, I document my findings. Your mileage may vary, it's not a copy/paste how-to.| Tobias Brunner aka tobru