Re:Go accepts patches from GitHub pull requests now
by frogperson on Monday February 12, 2018 @10:41PM
(#16364560)
I don't understand your point of view at all. Gerrit has such a good work flow and ui. It's probably in the top 5 best tools I have ever used. Github's pull request model is like a child's toy in comparison.
[ Parent
| on HN ]
Re:Go accepts patches from GitHub pull requests now
by labster on Tuesday February 13, 2018 @01:56AM
(#16365255)
Gerrit has a good UI? Heh, that's a good one. Git's CLI is like 10x superior to Gerrit's interface, and that's even counting the fact that git checkout does like 2 or 3 different things.
I've basically given up on fighting with the WMF's Gerrit install and outsource the work to other people. I push a commit up to a github repository, open a task, and ask another developer to grab my commit from a new git remote. I want to write code, not wrangle with whatever Gerrit wants me to do to submit code. And then look for tiny links on a cluttered page. No thanks.
Re:Go accepts patches from GitHub pull requests now
by xstartup on Tuesday February 13, 2018 @12:06AM
(#16364897)
Serious question, what are other best ones?
Re:Go accepts patches from GitHub pull requests now
by ithkuil on Tuesday February 13, 2018 @03:54AM
(#16365699)
I like https://reviewable.io, low friction github integration but gerrit-like multi-patchsets and generally a sane flow when you have multiple rounds of comments
Re:Go accepts patches from GitHub pull requests now
by vlovich123 on Tuesday February 13, 2018 @01:13AM
(#16365110)
I really enjoyed ReviewBoard when I used it but we built up a lot of tooling around it to actually make it useful & integrate into git.
Re:Go accepts patches from GitHub pull requests now
by u801e on Tuesday February 13, 2018 @11:35AM
(#16368404)
What is your opinion on just using a pure mailing list workflow (like what's done for git itself)?
Re:Go accepts patches from GitHub pull requests now
by nbsd4lyfe on Tuesday February 13, 2018 @08:16AM
(#16366857)
I'm assuming you're talking about the reviewer and long term contributor side of it. personally I found initial setup as a drive-by contributor to be very tedious. GitHub is the lowest friction because I already have an account with SSH key etc.