The only time I have seen WIP merges reviewed is when requested by the author or for a more junior engineer who may not understand the spec or codebase well. Th

The only time I have seen WIP merges reviewed is when requested by the author or for a more junior engineer who may not understand the spec or codebase well. They might actually improve developer velocity in this case with _paired programming_ until the engineer is up to speed - that or a more involved planning phase. Other than WIP reviews, I don't see any difference between pre-commit or post-commit reviewing - especially if they're both pre-deploy as described.