3 ms·
I hear this sort of remark a lot, but does anyone actually practice this? Like git is great in that there a myriad of options for syncing remotes, but none tha
by peeters 5y ago
I hear this sort of remark a lot, but does anyone actually practice this? Like git is great in that there a myriad of options for syncing remotes, but none that I've ever seen come close to having a central clone that also acts as the highest authority.
Having used git prior to Github et al, where I had remotes set up to literally each collaborator that they individually hosted, I would never want that user experience over what I have now. The centralized model is far too compelling. So I'm curious what the bleeding edge distributed model looks like today.
- radicality 5y agoI’m with you, I don’t even want the decentralised model, but it feels like with GitHub I get… the worst of both worlds? No decentralisation and crappy centralisation? For example, in a work environment, what’s even the point of ‘forking’ in GitHub. I don’t want my own version of any repo, I don’t want to be playing weird rebase/merge upstream/push origin nonsense. I don’t even want to be creating branches or naming branches. I just want a centralised repo: I make a commit and… that’s it, get a commit hash and be able to have that commit anywhere else I check out the repo, and open a PR/diff to merge into master.
- rezonant 5y agoI agree though that its hard to find use cases for forks in a typical business- however Unreal Engine would be a great example of it where the private repository is shared by multiple development teams. If you have access to it (because you've agreed to the Source License), you can make a private fork and send in a PR to the main repository. Epic probably won't merge it though unless you represent a big studio.