Migration from GitHub to Codeberg

[jschlatow]

This issue shall serve as an umbrella issue for the migration of the genode repository and all genode-* repositories to codeberg.org.

First of all, all issues and pull requests are going to be migrated to Codeberg along with the git repositories. The GitHub repositories will be archived (made read-only) and therefore will not receive any updates after the migration. Thus every user must update the repository URLs of any local clone. In the course of the migration, we are also going to change the name of the default branch from "master" to "main". Fortunately, both (changed URL, renamed branch) can be taken care of by the build system.

Users that still want to be able to contribute, must create an account at codeberg.org. It is possible to link the new account to your GitHub account. This enables Codeberg to associate your former comments (entered on GitHub) to your new account on Codeberg (i.e. you may use different user names on both platforms). In case you forked any repository on GitHub you should consider creating a new fork on Codeberg and manually pushing your branches and tags to the new fork. This can be achieved by creating a bare clone of the old repository and mirror-pushing (implies force push) to the new repository, e.g.:

$ git clone --bare https://github.com/<user>/<repo> goa_bare
$ cd goa_bare
$ git branch -m master main
$ git set-url origin ssh://git@codeberg.com/<user>/<repo>
$ git push --mirror

Codeberg uses Forgejo and has a very similar UI compared to GitHub. However, there are a few changes when it comes to referencing issues and commits. On Github you are able to push a commit referencing an issue via #<issue-number> to your fork and this commit will be shown in the corresponding issue of the original repository from which you forked. On Codeberg, however, you must explicitly mention the repository where the issue resides via genodelabs/genode#<issue-number>. Similarly, if you want to reference a commit from a fork in an issue comment, you must name the fork explicitly, e.g. jschlatow/genode@<commit-hash>.

[jschlatow]

Commit c44fd3f implements the check and automated adaptation of repository URLs. @nfeske please merge to staging.

[ssumpf]

@jschlatow: I just switched to current staging and experienced long waiting times when building a run script. Further inspection showed that there was no CPU/IO activity but quite a few curl instances with direction codeberg were running. The cause seems to be d406913. Is this intended behavior? Is there a way to disable the codeberg checks? I reverted the commit here for now.

[jschlatow]

@ssumpf Yes, this is - to some extent - intended. Curl is called for every repository that references github.com and genodelabs. Once the repository appears on Codeberg, the URL is automatically adapted and the curl call will be omitted. Since I'm migrating all repositories but the main repo to Codeberg very soon, there will only remain a single curl call until we also migrated the main repo.