Yes, Git was not designed for your workflow, that has a single remote and a special "main" branch. It was designed for a very different workflow used in Linux d

Yes, Git was not designed for your workflow, that has a single remote and a special "main" branch. It was designed for a very different workflow used in Linux development. Git just happened to be flexible enough to be a reasonably good fit for other workflows, including GitHub-centered workflow which is relatively common. Mostly because of easy branching/merging and great support for working off-line, I guess. However, it does not have built-in support for such workflows, their special requirements need to be be satisfied by tools and/or practices external to Git. What you are saying is that Git is not a perfect fit for your workflow, and that this workflow is fairly common, so why there is not something better for that need? If you stopped there, your post would be perfectly reasonable from my point of view. But you called your workflow "developer experience", as if that's the only one that exists. It's kind of offensive for the people with different workflows, and so with different experience. Anyway, I don't know the answer to your question, but my guess is that Git + external tools/practices is "good enough" for your workflow, so nobody created a completely separate system.