Merge Pull Request Command

Merge pull requests into a target branch with validation and quality gates.

3|1|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/nashgao/mqtt-client --skill merge-pull-request-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Merge Pull Request Command
Source: https://github.com/nashgao/mqtt-client/tree/main/.claude/skills/git/merge-pr
Command: npx skills add https://github.com/nashgao/mqtt-client --skill merge-pull-request-command

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This command streamlines the process of merging pull requests by incorporating essential validation and quality checks, ensuring code integrity and compliance before merging.

Core Features & Use Cases

  • Automated Validation: Checks for approvals, CI status, and merge conflicts.
  • Multiple Merge Strategies: Supports squash, merge commit, and rebase.
  • Branch Protection: Ensures compliance with repository rules.
  • Use Case: A developer wants to merge a feature branch into main. This command will automatically verify that the PR has the necessary approvals, all CI checks have passed, and there are no merge conflicts before proceeding with a squash merge.

Quick Start

Use the merge pull request command to merge the current branch's PR.

Frequently Asked Questions about Merge Pull Request Command

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

FAQPage Schema
How do I automate pull request merges with GitHub CI/CD validation?

Automating pull request merges involves using a command that validates approvals, CI status, and merge conflicts before executing the merge. This ensures code integrity and compliance with branch protection rules during GitHub automation.

What's the best way to ensure branch protection compliance before merging a pull request?

To ensure branch protection compliance before merging, you can use an automated validation process that checks repository rules and required approvals. This verifies that all quality gates are passed before the pull request is merged.

Can I choose between squash, merge commit, and rebase strategies when merging a PR?

Yes, you can choose between squash, merge commit, and rebase strategies when merging a pull request. The automated merge command supports all three methods, allowing flexibility in how commits are integrated into the target branch.

How does automated pre-merge checking work for GitHub pull requests?

Automated pre-merge checking works by verifying CI check statuses, required approvals, and identifying merge conflicts before proceeding. It integrates with the GitHub CLI to execute these quality gates safely and efficiently.

Does the automated merge command support automatic branch deletion after merging?

Yes, the automated merge command supports automatic branch deletion after merging. Alongside executing the pull request merge safely, it offers options to clean up the feature branch once the integration is complete.