Skip to content

reactive: Ensure latest pipeline is a merged results one

Rémy Coutable requested to merge 893-reactive-reminder-for-merged-mrs-without-a-full-merged-result-pipeline into master

What does this MR do and why?

In addition to checking that the latest pipeline is from the canonical project and recent enough, we also want to make sure it's a merge results pipeline.

This MR implements this.

Expected impact & dry-runs

ref is part of the simple pipeline API response.

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels =>
    • Engineering week-in-review

Closes #893 (closed).

Edited by Rémy Coutable

Merge request reports