<aside> 💡 惟客宝 gerrit 入口：http://gerrit.wakedata-inc.com/admin/repos

</aside>

Gerrit 会对你的每个 Commit 进行Review，只有通过 Review 才会被合并到正式分支。

1. 一些疑问

• 为什么不用 PR？

• 项目紧急、兼顾的项目多，能顾得上 Code Review吗？

• 学习成本高，冲突修复、驳回处理等操作流程比较麻烦，会不会影响效率？

• 为什么要Review？

  Code reviews can identify mistakes before they’re found by customers

  When code is reviewed, developers:

  • Work carefully and consistently
  • Learn best practices and new techniques from other developers
  • Implement consistency and quality across the code base

• Review 什么？

  Code reviews typically turn up issues related to:

  • Design: Is code well-designed and suited to the code base?
  • Functionality: Does code perform as intended and in a way that is good for users?
  • Complexity: Can other developers understand and use the code?
  • Naming: Does the code contain clear names for elements such as variables, classes, and methods?
  • Comments: Are comments specific and complete?

• 会不会互相阻塞？

  不会，每个提交都可以被独立 Review 和合并。如果你的功能依赖于其他开发者，应该在其他开发者提交合并之后合并。

• 学习成本是不是很高？

  有一定的学习成本，需要按照 Gerrit 的协议提交和 Review 代码。需要掌握一定的 Git 技术。不过这一切会值得