View all recipes

When unreviewed pull request merged assign debrief Task

When an unreviewed pull request is merged in Github, assign a Task for the author's manager to provide an explanation to your IT Security team.

How to minimize risk from unreviewed Github pull requests

With Rippling’s Workflow Automator, you can automatically assign a Task to a manager to explain to the IT security team when their team member merges a pull request that hasn’t been reviewed.

What do you need?

Rippling App Management


Use Recipe Template

Recipe Overview

The key benefit of a pull request (PR) is that it provides a space for teammates 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.

But 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 automatically assign a Task 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 our workflow Recipes, you can customize this template to your exact needs, including when it should trigger, what the actions should be, who it should go to, and more.

This recipe helps with

Functions that use this recipe

Companies that use this recipe

Similar Recipes