Hello everyone,
as outlined in our road map, we planned the migration of all but the
main (genode.git) repository from GitHub to Codeberg for the upcoming
26.02 release. I'm happy to announce that we just completed this
migration step. From now on, you'll find all genode-* repositories as
well as the Goa repository at
https://codeberg.org/genodelabs
Along with the git repositories, all issues, pull requests and comments
have been migrated as well. The repositories at GitHub have been made
read-only and therefore will not receive any updates. In the course of
the migration, we have also changed the name of the default branch from
"master" to "main".
In order to adapt to these changes on your side, we advise you to switch
to the current master branch in your clone of
https://github.com/genodelabs/genode.git and follow the instructions
that are printed by any build command. For Goa, you can trigger the
migration with the following commands:
goa update-goa master
goa versions
Note that the migration to Codeberg implies a few more changes for
contributors: Contributors 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 to restore the state of the forked
repository as it was on GitHub. The following instruction serve
as a guideline:
git clone --bare https://github.com/<user>/<repo> bare_clone
cd bare_clone
git branch -m master main
git remote set-url origin ssh://[email protected]/<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, e.g., genodelabs/goa#<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/goa@<commit-hash>.
Cheers
Johannes
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Archived at
https://lists.genode.org/mailman3/hyperkitty/list/[email protected]/message/6TKDRIJXOMGURM7SIZJAAP5TSVP443WJ/
