Setup is simply 3 steps:
1. Sign up on each service, ideally with the same username.
2. For each repo you want to share, create the same repo name as a blank repo; do not automatically create a README.
3. Edit your local file .git/config to add push URLs, then push as usual.
Example:
[remote "origin"]
url = git@github.com:foo/bar.git
pushurl = git@codeberg.org:foo/bar.git
pushurl = git@github.com:foo/bar.git
pushurl = git@gitlab.com:foo/bar.git
fetch = +refs/heads/*:refs/remotes/origin/*Usually the argument is for scalability, but a single VM for personal use doesn't need that, and even if you do want that, you'll need more than a bare repo.
> This is a lie. Github - and the microsoft organization more widely - clearly prioritize flashy AI features over fundamental reliability Github has a public changelog. In thirty days since they posted their update, their patch notes contain the words “copilot” 59 times, “agent” 8 times, “performance” 0 times, and “reliability” 0 times. The changelog has a feature to filter by category: copilot is it’s own category: performance and reliability do not exist at all.
I suppose when calling someone a liar, it's beneficial to have hard numbers to back it up. Ouch.
It’s fascinating to me that the people who know the most about tech keep deciding over and over to give something to some corporation and inevitably it becomes an issue. I guess ease of use and freemium really trumps everything; I expect more from smart people but money talks.
Heck, GH Stars are used as a vanity metric for a lot of projects.
Self hosted gitlab is a dream, no surprises ever, exactly how your repos are supposed to work.
rglover•39m ago
— Charlie Munger
Edit: great write up, thank you op.