The key benefit of a pull request (PR) is that it provides a space for team members to discuss potential changes before they’re officially merged – that way, every change gets multiple pairs of eyes on it, to ensure it’s error and risk-free.

However, sometimes, a team may choose to merge a PR without it having had its due review, posing a risk not just to the quality of the feature, but to the company’s overall infrastructure as well.

So, when a risk like that is taken, it’s best practice to have your Security team investigate and ensure the decision wasn’t improperly made.

With this Recipe, you’ll be able to ensure that unreviewed merges don’t slip through the cracks undetected. When a PR in GitHub is merged without review, Rippling will assign a Task automatically to the author’s manager to explain why the unreviewed merge occurred.

Want an alert sent to your #it-security channel as well? As with all of our workflow Recipes, you can customise this template to your exact needs, including when it should trigger, what the actions should be, who it should go to and more.