Send small PRs (Google eng-practices)(google.github.io)
google.github.io
Send small PRs (Google eng-practices)
https://google.github.io/eng-practices/review/developer/small-cls.html
3 comments
Google ought to spend effort on understanding and then explaining how to chunk large pieces of work that don't seem to qualify. Recommending that an engineer asks their peers for help shows that management also has no idea how to chunk the work.
What is a CL?
Change list, essentially equivalent to a PR. Gerrit also uses them so it's a good place to check for the differences (squashing of commits into single CL for example)
CL stands for change list.
It's the unit of change that goes through code review (so for the context of that document I think the best translation to the git world is PR).
Though it's not exactly a PR, a CL is also a single change in the change history (so you could also say that a CL is equivalent to a commit)
It's the unit of change that goes through code review (so for the context of that document I think the best translation to the git world is PR).
Though it's not exactly a PR, a CL is also a single change in the change history (so you could also say that a CL is equivalent to a commit)
What they aren't good at is to show the overall intent of the whole change. I.e. what I've found is that sometimes an individual PR is easy to review and approve because it seems innocuous and totally fine. But in the overall grand scheme of things I'd have "questions". I might even question the overall concept of the whole thing but I don't have the full picture and what seems innocent as a small PR is actually going towards a grand vision I can't support.
I won't deny that I've used the same technique to get otherwise probably more controversially discussed stuff through ;)