As specified by the pipeline model we described in Chapter 4, Creating a Pipeline and Workflow, the candidate code moves through a series of stages, stopping if there's a problem.
As we mentioned previously, reviewing using GitHub pull requests works if we wish to introduce new features to the code of our microservices, as well as if we wish to deploy those changes into clusters through GitOps practices.
In both cases, we can check this automatically through automated tests and processes. However, there's a final step that requires manual intervention: knowledge transfer and an extra pair of eyes. Once the reviewer thinks the new feature is ready, they can approve it.
The tools are the same, although the reviewing process works a little differently. This is because the objectives aren't the same. For feature code, the review...
