This is an adaptation of the original Google’s Code Review Guidelines, to use GitHub specific terminology. Google has their own internal tools for version control (Piper) and code review (Critique). They have their own terminology, like “Change List” (CL) instead of “Pull Request” (PR) which most developers are more familiar with. The changes are minimal and the content is kept as close to the original as possible. The hope is to make this gem accessible to a wider audience. I also ...| Onur Solmaz blog
Practices worth adopting for other organizations| addyo.substack.com
Why Should We Measure Engineering Productivity?| abseil.io