3 ms·

I like Gerrit features, but it always seemed too complicated to integrate into usual coding workflow, especially with people always even complaining about git b

I like Gerrit features, but it always seemed too complicated to integrate into usual coding workflow, especially with people always even complaining about git being "hard to use". This tools seems simpler compared to Gerrit, and more flexible compared to GitHub pull requests. I would appreciate advices on introducing Gerrit to my team and make it somehow transparent in development workflow.

alblue 11y ago
I wrote about Gerrit a few years ago: http://alblue.bandlem.com/2011/02/someday.html http://alblue.bandlem.com/2011/02/someday.html I recorded a video showing how it worked together: http://alblue.bandlem.com/2011/02/gerrit-git-review-with-jenkins-ci.html http://alblue.bandlem.com/2011/02/gerrit-git-review-with-jen... Once you understand the workflow it's actually easy to adopt. The biggest challenge is getting people to think in terms of push requests instead of pull requests. If you configure the remote as "git config push HEAD:refs/for/master" then it becomes as simple as doing "git push" to upload changes.