backport-pr

Name: backport-pr
Availability: InStock
Author: Microsoft

Automate GitHub PR backports to Aspire release branches with shiproom approval updates.

6.2k|952|Updated Sep 25, 2023

Search Tags:#automation #github #pull requests #observability #backport #release branches #shiproom template

Ready to run

npx skills add https://github.com/microsoft/aspire --skill backport-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backport-pr
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/backport-pr
Command: npx skills add https://github.com/microsoft/aspire --skill backport-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you backport a merged PR to a specific Aspire release branch and prepares the required shiproom approval template so the backport can be reviewed quickly.

Core Features & Use Cases

Triggers the backport workflow by posting the correct /backport comment on the source PR when no backport attempt exists yet.
Waits for the backport bot to create the backport PR on the predictable head branch, including handling in-progress and failure states.
Fills the shiproom template (Customer Impact, Testing, Risk, Regression?) on the resulting backport PR using context from the source PR and linked issues.

Quick Start

Ask the AI to backport PR 1234 to release/13.3 and fill the shiproom template on the resulting backport PR.

Frequently Asked Questions about backport-pr

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

FAQPage Schema

How do I backport a GitHub pull request to a release branch?▼

Backporting a GitHub PR to a release branch is automated by triggering the /backport bot on the source PR, which creates a cherry-picked backport PR on the target branch. This requires providing the source PR number and the specific release branch name.

How do I fill the shiproom template on a backport PR?▼

Filling the shiproom template on a backport PR is automated by inserting required approval sections like Customer Impact, Testing, Risk, and Regression using context from the source PR. This ensures template insertion occurs without overwriting any unrelated manual content already present.

What is the process for backporting fixes to Aspire release branches?▼

Backporting fixes to Aspire release branches involves triggering the /backport bot, polling for the predictable backport PR head branch, and completing shiproom metadata. This servicing workflow requires shiproom approval sections to be filled before the backport can be merged.

Can I use a manual backport PR with this automation?▼

Yes, manual backport PRs are supported through optional handling for existing backport attempts. The automation can locate an existing backport PR head branch and proceed to update its shiproom approval sections without triggering a new backport workflow.

Does the backport automation handle in-progress or failed bot states?▼

Yes, the backport automation waits for the backport bot by polling with authoritative success signals. It actively handles both in-progress states and failure states while locating the predictable backport PR head branch on the target release branch.