"value":"\n <p>If your team wants or needs to do code reviews, but you don't want it to slow down development, you could implement non-blocking code reviews.<\/p>\n\n<p>Instead of creating a topic branch for a feature or fix, creating a pull or merge request and waiting for it to be reviewed before merging, the commit is merged, and the code is reviewed afterwards.<\/p>\n\n<p>The ticket workflow could look like this:<\/p>\n\n<p>To Do -> Doing -> Merged -> Reviewed -> Tested -> Deployed<\/p>\n\n<p>Or:<\/p>\n\n<p>To Do -> Doing -> Merged -> Deployed -> Tested -> Reviewed<\/p>\n\n<p>The focus is getting the update to production, and the review is deferred.<\/p>\n\n<p>The same CI pipeline rules apply - it must be passing before the code can be deployed, so the same quality checks are run.<\/p>\n\n<p>With this approach, the code is still reviewed, either in the pull or merge request or by the commits on the mainline branch if doing trunk-based development. It's just done later.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>If your team wants or needs to do code reviews, but you don't want it to slow down development, you could implement non-blocking code reviews.<\/p>\n\n<p>Instead of creating a topic branch for a feature or fix, creating a pull or merge request and waiting for it to be reviewed before merging, the commit is merged, and the code is reviewed afterwards.<\/p>\n\n<p>The ticket workflow could look like this:<\/p>\n\n<p>To Do -> Doing -> Merged -> Reviewed -> Tested -> Deployed<\/p>\n\n<p>Or:<\/p>\n\n<p>To Do -> Doing -> Merged -> Deployed -> Tested -> Reviewed<\/p>\n\n<p>The focus is getting the update to production, and the review is deferred.<\/p>\n\n<p>The same CI pipeline rules apply - it must be passing before the code can be deployed, so the same quality checks are run.<\/p>\n\n<p>With this approach, the code is still reviewed, either in the pull or merge request or by the commits on the mainline branch if doing trunk-based development. It's just done later.<\/p>\n\n ",