I am currently preparing the migration of this repository to codeberg.org. In order to render this as seamless as possible for Goa users, I'd like to document the steps taken in this issue and integrate a mechanism into Goa for updating the git URL.
First of all, all issues and pull requests are going to be migrated to Codeberg along with the git repository. The GitHub repository will be archived (made read-only) and therefore will not receive any updates after the migration. Thus every Goa user must update the remote URL used by the local clone of the Goa repository. 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 Goa. For the user, the migration will be as simple as updating to the latest version from GitHub and executing any Goa command afterwards (which will trigger the migration), e.g.:
$ goa update-goa master
$ goa versions
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 the Goa repository on GitHub you should consider creating a new fork on Codeberg and manually pushing your branches and tags to the new fork. (Detailed instruction will be added at a later point in time.)
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/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>.
I am currently preparing the migration of this repository to codeberg.org. In order to render this as seamless as possible for Goa users, I'd like to document the steps taken in this issue and integrate a mechanism into Goa for updating the git URL.
First of all, all issues and pull requests are going to be migrated to Codeberg along with the git repository. The GitHub repository will be archived (made read-only) and therefore will not receive any updates after the migration. Thus every Goa user must update the remote URL used by the local clone of the Goa repository. 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 Goa. For the user, the migration will be as simple as updating to the latest version from GitHub and executing any Goa command afterwards (which will trigger the migration), e.g.:
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 the Goa repository on GitHub you should consider creating a new fork on Codeberg and manually pushing your branches and tags to the new fork. (Detailed instruction will be added at a later point in time.)
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 viagenodelabs/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>.