Release gating with pull requests
As we saw in the previous section, the CI pipeline built the code, did a test, ran a container, and verified that everything is OK. It then automatically raised a pull request to merge the code with the master branch. Now, we're in the release gating process. We want someone to manually verify whether the code is good and ready to be merged with the master branch or not. Apart from the CI workflow, we'll also use release gating in the Continuous Deployment (CD) workflow. As we know that the pull request is raised, let's go ahead and inspect the pull request and approve it.
Go to https://github.com/<your_user>/flask-app-gitops/pulls and you will see a pull request. Click on the pull request, and you will see the following:
Figure 14.3 – Pull request
We see that the pull request is ready to merge. Click on Merge pull request, and you will see that the changes will reflect onto the master branch...
