"value":"\n <p>Code review with pull and merge requests is great for open-source but not for development teams or soloists.<\/p>\n\n<p>On an open-source project, the code changes are most likely being submitted by someone you don't know and don't work with regularly, so having a step to review the code prior to merging it and decide if you want to take on the responsibility of maintaining it is a big decision.<\/p>\n\n<p>On a development team, you work closely with the person submitting the change request and you have a shared responsibility and ownership of the code being added. The person isn't going to submit their change and not be seen again.<\/p>\n\n<p>It takes time for code to be reviewed, which means it takes longer for the change to be released to users.<\/p>\n\n<p>If you're a soloist, are you going to submit a request for you to review your own code?<\/p>\n\n<p>If you don't need to do code review on your team, do you need to create feature or topic branches?<\/p>\n\n<p>I'd suggest sticking to one canonical branch and doing trunk-based development instead.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>Code review with pull and merge requests is great for open-source but not for development teams or soloists.<\/p>\n\n<p>On an open-source project, the code changes are most likely being submitted by someone you don't know and don't work with regularly, so having a step to review the code prior to merging it and decide if you want to take on the responsibility of maintaining it is a big decision.<\/p>\n\n<p>On a development team, you work closely with the person submitting the change request and you have a shared responsibility and ownership of the code being added. The person isn't going to submit their change and not be seen again.<\/p>\n\n<p>It takes time for code to be reviewed, which means it takes longer for the change to be released to users.<\/p>\n\n<p>If you're a soloist, are you going to submit a request for you to review your own code?<\/p>\n\n<p>If you don't need to do code review on your team, do you need to create feature or topic branches?<\/p>\n\n<p>I'd suggest sticking to one canonical branch and doing trunk-based development instead.<\/p>\n\n ",