GitLab MR reminder
GitLab MR reminder
Schedule reminders and never let your GitLab Merge Requests go stale.
By
DevRev

GitLab MR reminder

Schedule reminders and never let your GitLab Merge Requests go stale.

Overview

image

Stay on top of your code reviews by scheduling reminders when an MR is inactive for a certain period. You can enable this automation for all of your GitLab repos, or for specific repos. When you enable GitLab autonomous work, MR reminders are scheduled to be posted on linked issues. You may also enable the GitLab MR Task automation that creates a task for every MR.

How it works

To use this automation, you'll need to connect your GitLab with DevRev so we can listen to MR events. When you install this flow, we'll walk you through a few simple steps to connect and setup your reminders. You can find more on the supported connection methods here.

Features

Post reminders on your DevRev issues, when related GitLab Merge Requests are inactive for a certain period.

Automatic MR reminders

When a merge request is inactive for more than a specified number of days, then this automation will post a message in all related DevRev issues. You'll need to link your GitLab Merge Request to DevRev issue to enable these reminders. There are several ways to link your GitLab Merge Requests to DevRev Issues. You can do so by mentioning the DevRev issue-id in Merge Requests title or body, or mention it in the branch name or commit message. Reminders are also posted for issues created autonomously.

You can choose to setup the inactive period in number of days through the max_inactive_days setting.

Frequently asked questions

What are the prerequisites for scheduling MR reminders?This automation is triggered when Merge Requests are linked to DevRev issues. If you have not linked GitLab Merge Requests, then reminders will not be posted.