4 ms·
A patch/diff workflow operates at the level of individual diffs, rather than a branch identified by base and head refs like with pull requests. Email is one (v
by lima 6y ago
A patch/diff workflow operates at the level of individual diffs, rather than a branch identified by base and head refs like with pull requests.
Email is one (very clunky) way of implementing such a workflow, there's other tools like Gerrit, Reviewable or Phabricator that are more friendly.
- da39a3ee 6y agoThanks. Can you explain why that might be a good thing? If I update the diff, does it become a new reviewable item, independent from the first version? I've never worked at a large tech company but my understanding is that at e.g. google there is some sort of monorepo, so it would presumably zoom forwards while a commit is under review. Even so, why is it not a good thing to review the commit in an explicit location in the historical commit graph?
- lima 6y agoPatches would still have a base, it's really more about about the data model. It's possible to synthesize a GitHub PR from a Gerrit CL and vice-versa. In fact, Gerrit is entirely based on Git and you can simply clone any given CL.