Default avatar
Carlos 2 years ago
Why not just host a Gitea instance as intermediary step? Low hanging fruit: simple to install and 100% compatible with GH workflows (PRs, SSO, comments, etc). Removes dependency on GH until a proper replacement shapes up.

Replies (1)

This is exactly what I do and recommend. Everyone writing code should be handling their primary/authoritative git served in house, and use GitHub, GitLab, Bitbucket, AWS Code, Sourceforge,Launchpad etc as mirrors only. Gitea works ok at small scale. One caveat is when pushing commits to mirrors the refs to issues won't line up and this can be confusing in GitHub and others that render links The bigger challenge is projects that are intended to be open and decentralized like Bitcoin. They need a publicly accessible authoritative home without risk of a single corporate or gov organization controlling, or being rugpulled. I periodically fetch and backup projects I deem important, and recommend also running local maven and npm registries as needed