|
|
|
|
|
by arjie
3730 days ago
|
|
It needs the context. I've quoted the whole thing below: > If you add a new member to your team, they would have to fork the repositories on GitHub, clone them locally, make the changes, push to their own fork and then create the pull request. With Gerrit, you could clone the main repository, do your change and then push it directly to the same remote as you cloned it from. The objection would be that you can always push to a branch and issue a PR from there in GitHub too. Those steps are identical for both tools in a professional setting. There are reasons for Gerrit but this isn't one. |
|