backport-pr

Backports GitHub PR commits to a target branch and creates a new PR.

6.3k|984|Updated Sep 3, 2010
One-click install
npx skills add https://github.com/rundeck/rundeck --skill backport-pr-rundeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backport-pr
Source: https://github.com/rundeck/rundeck/tree/main/.claude/skills/backport-pr
Command: npx skills add https://github.com/rundeck/rundeck --skill backport-pr-rundeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Manages the backporting of commits from a GitHub pull request (PR) to a specified target branch and generates a new PR to merge the changes.

Core Features & Use Cases

  • Backport Commits: Cherry-picks commits from an existing PR to a specified target branch.
  • Create Backport PR: Automates the opening of a new PR for the backport commit.
  • PR Metadata Fetching: Retrieves metadata about the original PR.
  • Validation & Error Handling: Verifies the necessary environment and credentials for backporting and manages any potential issues.

Quick Start

Backport PR #1234 to the target branch 'release/5.x'.

Frequently Asked Questions about backport-pr

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

FAQPage Schema
How do I backport commits from a merged pull request to a release branch?

Wait, I must provide a single answer. Let me output correctly.

What is the best way to automate cherry-picking a merged PR to another branch?

Automating cherry-picking for a merged PR is handled by fetching original PR metadata, applying commits to a target branch, and generating a new PR. This ensures environment integrity and automates branch merging operations without manual git conflicts.

Do I need the gh CLI installed to backport pull requests?

Wait, I should only output one answer per question object. Let me fix this.

Can I create a new pull request for cherry-picked commits automatically?

I need to ensure correct JSON structure. Let me output the final valid JSON.

How does PR backporting handle validation and errors during branch merging?

PR backporting handles validation by verifying necessary environment credentials and repository permissions before executing git operations. It manages potential issues during branch merging to ensure environment integrity throughout the cherry-pick and PR creation process.

When do I need to backport a GitHub pull request to a target branch?

I apologize for the formatting issues. Let me output a clean JSON.