But, there are? I can host a repo on GitHub, Codeberg and self host it too. Then I need to watch over main to keep it consistent between those. After that's established, I can do updates from wherever. Link'em in the README.

▲

nibbleyou 3 hours ago | parent | next [-]

There's also a tool to automatically push it to multiple repos: https://github.com/prashantsengar/GitEcho

Disclaimer: the author is a colleague of mine

Though to be fair, what the parent meant by federated forges is different than this approach.

	▲	pabs3 an hour ago \| parent [-]
		git itself can push to multiple URLs btw: https://stackoverflow.com/questions/849308/how-can-i-pull-pu...

▲

embedding-shape 2 hours ago | parent | prev [-]

There are distributed forges? Yes, git is distributed, but often everything around it isn't. The case parent is trying to make, is that the rest ("federated forges") should also be distributed, not just git.

▲

ArcHound 2 hours ago | parent [-]

Ok, gotcha. So there's a demand for the additional features that are not bundled within git to be federated somehow.

I'd say we have emails, mailing lists and bug trackers. Or maybe: what is the missing killer feature that needs federation?

	▲	embedding-shape 2 hours ago \| parent [-]
		> what is the missing killer feature that needs federation? Issues, pull requests, collaboration/permissions/access, "staring"/"favoriting", etc. I think ultimately the goal is that people can run their own forges, yet still collaborate on repositories hosted in other forges, leveraging your existing authentication so you no longer need to sign up individually for each forge.