729
Merge then review
(programming.dev)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Ugh, not this SAFe Agile (tm) cultist bullshit. The "value" is working, bug free code, which you get when you put it through review and QA before it gets to production.
There's often features and bug fixes worth more than the ones introduced in the PR. I've yet to see bug free code just because it's went through review and QA.
Surely you've seen bugs caught because code went through review and QA though. Those are bugs that would go into production if following the "advice" in this post.
I'm saying identify the bugs through review, and fix them. Just do it in a new PR unless they are critical