To be fair, Forgejo, the software that Codeberg runs, has pretty much all the features Github has.
Its interface is very similar, the CI/CD system is compatible with Github Actions, and it has unique features like automatic mirroring of repositories to/from github, gitlab and other forges, so that you dont need to maintain your own tools for that.
But also dont forget that if/when you would use paid features of Github, the same could be available on Codeberg or other Forgejo instances too, and supporting them with the same amount of money may be better for the common good.
You dont need to maintain your own scripts for that, unless you want to continuously migrate issues and other items too. Codeberg can do the git sync automatically.
If you create a migration instead of a new repo:
and then select github, you can migrate repos by passing a git url.
By default it would create the mirror repo in your user account, but you can select an org where you are a member.
Providing an access token is probably not necessary, unless you also want to migrate those additional items, but be aware that for now those wont be kept in sync after the initial migration.
Later you will be able to change the sync interval in the repo settings.
And surely it is better to invest the effort in so many interesting technological topics that there are to advance in OpenWRT than to waste time leaving GitHub...
I am not monitoring the forum. Most devs do not look at the forum. Infrastructure discussions are either done on the public mailing list or in IRC.
The main repository is still at git.openwrt.org, github is just a mirror. Currently we get most of the contributions over github, it looks like most contributors prefer github over the mailing list. All commits are pushed to git.openwrt.org, a script on this server then mirrors it to github.
