I'm going to (generously) assume that author means to immediately merge into a development or feature branch and review later before merging those commits somew

I'm going to (generously) assume that author means to immediately merge into a development or feature branch and review later before merging those commits somewhere else. If so, sure that probably saves time. Most reviews should be uneventful anyway and it broadens the scope of review to the whole branch. That's helpful when you have lots of moving parts and multiple devs working on the same feature. My opinion on this is that code review must occur especially if there is no other form of review. That's usually more technical projects where the devs are left alone. Contrary to popular belief there really are some projects so short-lived, truly throwaway code such as light web dev (marketing pages and whatnot), that final proofreading and QA are good enough.