问题
Using a shared repository model. In short:
- we want to be able to review code changes
- but, we don't want pull requests to hold up integration at all
I've used a workflow like this in the past with Code Collaborator, but I don't think it was with Git(?). The point is to allow quicker code integration, while at the same time providing some review of code changes. If the review finds issues, the developer just fixes the issues and integrates, updating the code review in the process. Once the code review is done, there's no "pull" (merge): the code is already merged; the review just gets closed.
回答1:
You still can consider Gerrit for your review process.
It even has an "auto-merge during Push" which would allow you to merge immediately, while retaining a spot where to conduct your review.
As commented, this is not the ideal workflow, but the point is: you can configure Gerrit in multiple ways.
来源：https://stackoverflow.com/questions/46984668/github-code-review-without-pull-request