4 ms·
You have slightly illustrated it yourself in a roundabout way, but let's be clear with wording here: > The design of git makes switching to another primary rem
by Klonoar 3y ago
You have slightly illustrated it yourself in a roundabout way, but let's be clear with wording here:
> The design of git makes switching to another primary remote very easy
It is never as easy as just switching to another primary remote.
It's not just Issues/Wikis/Releases, but the build/CI process(es) that are rampant on GitHub now, the community you've built potentially coming up on GitHub and not really getting that there's anything else out there, etc.
This is all time consuming hard work. People will often just not do it, and this is why we have lock in everywhere. Stop calling it easy.
The centralization of the internet around a few specific services - like GitHub, Cloudflare, and so on - is an increasingly problematic thing to contend with.
Edit: "as a easy" -> "as easy"
- dboreham 3y agoQuick data point: while not exactly trivial, my team has migrated completely from github to our own hosted gitea. Including CI, releases, issues, read-only mirror back to GitHub, PRs etc. The only thing we don't have that would be nice is the ability to take a PR directly from a fork of a repo in someone else's Gitea deployment (or GitHub for that matter). To take an external PR we either need to recreate it manually in our Gitea under a team member's account, or give the external contributor an account on our Gitea.