Verified:GitHub

merge-requests

List, inspect, create, and merge GitLab merge requests with SHA guards.

Updated Apr 10, 2026

Search Tags:#automation #merge #gitlab #code-review #ci #merge-requests #sha-guard

One-click install

npx skills add https://github.com/theslashdojo/dojo --skill merge-requests

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: merge-requests
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/gitlab/merge-requests
Command: npx skills add https://github.com/theslashdojo/dojo --skill merge-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual friction of opening, inspecting, and merging GitLab merge requests so agents and automation can reliably start and complete code review and merge workflows after branches are pushed.

Core Features & Use Cases

List and Inspect MRs: Query project merge requests and fetch detailed merge status to decide if an MR can be merged.
Create MRs: Open a merge request from a prepared source branch to a target branch with options like reviewers, labels, squash, and remove source branch.
Merge Safely: Perform guarded merges using an expected HEAD SHA, optional squash, remove-source-branch behavior, and auto-merge controls for CI-driven workflows.
Use Case: An autonomous CI job detects a ready branch, creates a draft or regular MR, waits for pipeline success, and merges with a SHA guard to avoid unreviewed commits landing.

Quick Start

Create a merge request in project group/project from branch feature/refactor into main titled Refactor deploy flow, enable squash, and remove the source branch.

Frequently Asked Questions about merge-requests

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

FAQPage Schema

How do I automate GitLab merge request creation from a pushed branch in CI?▼

To automate GitLab merge request creation, provide a project path, source branch, target branch, and an authentication token like GITLAB_TOKEN or CI_JOB_TOKEN to open an MR with options for reviewers, labels, and squash.

What is a SHA guard when merging a GitLab merge request?▼

A SHA guard is an expected HEAD SHA value used during a GitLab merge to ensure no new commits were added after review, preventing unreviewed code from landing during release workflows.

Can I check merge request pipeline status before merging in GitLab automation?▼

You can inspect merge request details to fetch pipeline and merge status, allowing CI automation to decide if an MR is ready to be merged safely before executing the merge action.

What authentication tokens work for GitLab merge request automation?▼

GitLab merge request automation supports GITLAB_TOKEN, OAUTH_TOKEN, or CI_JOB_TOKEN to authenticate API requests for listing, creating, inspecting, and merging merge requests.

How do I automatically remove the source branch after a GitLab merge?▼

When creating or merging a GitLab MR, enable the remove-source-branch option to automatically delete the source branch after the merge completes, keeping the repository clean.

Does GitLab merge request automation support squash commits during CI workflows?▼

GitLab merge request automation supports enabling squash to combine all source branch commits into a single commit on the target branch during a guarded merge in CI-driven workflows.