retrigger-mr-pipeline

Create a new merge_request_event pipeline for a GitLab merge request.

Updated Aug 23, 2026

Search Tags:#pipeline #gitlab #ci #glab #mr #merge_request #retrigger

One-click install

npx skills add https://github.com/taptap/agents-plugins --skill retrigger-mr-pipeline

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: retrigger-mr-pipeline
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/git/skills/retrigger-mr-pipeline
Command: npx skills add https://github.com/taptap/agents-plugins --skill retrigger-mr-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a new merge_request_event pipeline for a GitLab merge request when retrying jobs does not pick up updated include templates, ensuring CI jobs run with the latest configuration.

Core Features & Use Cases

Create MR pipeline: Use the GitLab MR pipelines API to create a fresh merge_request_event pipeline for a specific merge request.
Flexible input handling: Accept MR web URLs or infer MR IID and project from the repository remote to locate the target MR.
Use case: Run this when CI include templates were updated or reviewer jobs must be rerun and a retry would not fetch new templates.

Quick Start

Use the retrigger-mr-pipeline skill to create a new pipeline for the merge request at https://gitlab.com/namespace/project/-/merge_requests/123.

Frequently Asked Questions about retrigger-mr-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trigger a new pipeline for a GitLab merge request instead of retrying jobs?▼

You can create a new merge_request_event pipeline by providing the MR web URL or inferring the MR IID from repository remotes to POST to the GitLab MR pipelines endpoint, bypassing cached include templates.

Why does retrying a GitLab CI job not pick up updated include templates?▼

Retrying GitLab CI jobs reuses cached include templates from the original pipeline execution. To pick up updated CI template changes, you must create a fresh merge_request_event pipeline via the MR pipelines API.

Do I need GitLab Premium to create a new pipeline for a merge request?▼

Yes, triggering a new merge_request_event pipeline via the MR pipelines endpoint requires GitLab Premium API access to authorize the POST request for the merge request.

What input formats does the retrigger-mr-pipeline skill accept to locate the merge request?▼

The skill accepts direct GitLab MR web URLs or infers the MR IID and project namespace from the repository remote configuration to locate the target merge request for pipeline creation.

When should I create a new MR pipeline instead of using the GitLab retry function?▼

Create a new MR pipeline when CI include templates are updated or reviewer jobs need rerunning, because the standard GitLab retry function will not fetch the new template configurations.