Verified:GitHub

gitlab-create-merge-request

Create a GitLab merge request using the first commit message as the title.

2|2|Updated Jan 5, 2021

Search Tags:#automation #git #CLI #GitLab #merge-request #glab

One-click install

npx skills add https://github.com/kentoje/dotfiles --skill gitlab-create-merge-request

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-create-merge-request
Source: https://github.com/kentoje/dotfiles/tree/main/.config/claude/skills/gitlab-create-merge-request
Command: npx skills add https://github.com/kentoje/dotfiles --skill gitlab-create-merge-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a GitLab Merge Request (MR) for the current branch by using the glab CLI and sets the MR title to the first commit message on the branch, streamlining merge workflows in GitLab.

Core Features & Use Cases

Automated MR Creation: Generate a GitLab MR with a meaningful title derived from the first commit message.
Branch Workflow Support: Ideal for feature branches targeting main, enabling one-step MR creation during code reviews and release prep.
Use Case: After finishing a feature on a new branch, run this skill to open an MR in GitLab using the first commit message as the MR title.

Quick Start

Ensure glab CLI is installed and authenticated. Get the first commit message: git log main..HEAD --reverse --format="%s" | head -n 1 Create the MR: glab mr create -t "<FIRST_COMMIT_MESSAGE>" -d "<SUMMARY_OF_WHAT_HAS_BEEN_DONE>" -b main --fill -y Push the branch if not pushed: git push -u origin <branch>

Frequently Asked Questions about gitlab-create-merge-request

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

FAQPage Schema

How do I create a GitLab merge request using the first commit message as the title?▼

To create a GitLab merge request with the first commit message as the title, this skill uses the glab CLI to automatically extract the initial commit subject and apply it to the MR. It streamlines MR creation for feature branches targeting main.

How do I automate merge request creation for feature branches in GitLab?▼

You can automate merge request creation for feature branches by running this skill, which relies on glab CLI and Git to open an MR targeting main. It formats the MR title from the initial commit message to streamline code reviews.

Do I need glab CLI installed to automate GitLab MR creation?▼

Yes, you need the glab CLI installed and authenticated to automate GitLab MR creation. This skill relies on glab CLI and Git, requiring proper repository access and the current feature branch to be pushed if needed.

What's the best way to set an MR title from a commit message in GitLab?▼

The best way to set an MR title from a commit message in GitLab is using this skill, which retrieves the first commit message via Git and passes it to glab CLI. This ensures a meaningful, automated MR title derived from initial branch work.

Why does my GitLab merge request automation require the branch to be pushed?▼

GitLab merge request automation requires the branch to be pushed because the remote repository needs the latest commits to create the MR. This skill relies on Git and glab CLI, necessitating that the current branch is pushed to origin if it has not been already.