logoalt Hacker News

stavrostoday at 9:32 AM3 repliesview on HN

But why doesn't Gitea add it? It already has everything else, why are these forges always Github clones instead of doing more?


Replies

Aeoluntoday at 11:59 AM

Well, if you are building one you generally want to support the 99% workflow, not the experimental one.

What part of gerrit is so different? Stacked PR’s work fine right (not in github, as a concept)

show 1 reply
corvadtoday at 9:39 AM

My best guess is lack of resources and that they want to focus on the well known PR workflow instead of trying new things out of the gate. It's exactly that, it's a proven github workflow for better or for worse that most people are familiar with.

cmrdporcupinetoday at 12:39 PM

There's two reasons.

1. Gerrit's approach requires a stable Change-Id in the commits. So it doesn't just work out of box with stock git. It requires that the submitter's git configuration and the repository be set up to support this. (Note that JJ supports this out of the box)

2. Cargo cult. We have a whole generation of software developers who grew up in this generation, love GitHub, and have never known anything else. The "PR" approach is considered orthodox. Unless they went and worked at a Google or somewhere like that, they've probably never been exposed to alternative processes.