skills.rest
NVIDIA
NVIDIAOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

3.4k|535|Updated Apr 23, 2024
Search Tags:#git#release management#github#pull requests#cherry-pick#backport
One-click install
npx skills add https://github.com/NVIDIA/Model-Optimizer --skill release-cherry-pick-nvidia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-cherry-pick
Source: https://github.com/NVIDIA/Model-Optimizer/tree/main/.agents/skills/release-cherry-pick
Command: npx skills add https://github.com/NVIDIA/Model-Optimizer --skill release-cherry-pick-nvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of moving approved merged pull requests from the main branch into release branches, reducing manual release preparation errors and coordination overhead.

Core Features & Use Cases

  • Release PR Selection: Finds merged pull requests with the correct cherry-pick labels while excluding already processed changes.
  • Automated Cherry-pick Workflow: Guides branch setup, commit retrieval, ordered cherry-picking, conflict handling, and release PR creation.
  • Use Case: Prepare a software release by collecting all pending cherry-pick requests for a specific version, applying them to the release branch, and marking completed pull requests.

Quick Start

Use the release-cherry-pick skill to cherry-pick all pending labeled pull requests for release version 0.44.0 into the corresponding release branch.

Frequently Asked Questions about release-cherry-pick

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

FAQPage Schema
How do I automate cherry-picking merged pull requests into a release branch?▼

Automated cherry-picking of merged pull requests into a release branch selects labeled PRs, retrieves merge commits, and applies them sequentially. It handles branch setup, conflict resolution, and creates the final release pull request.

What is the best way to manage backport workflows for software release management?▼

Managing backport workflows for software release management involves finding merged pull requests with specific cherry-pick labels. This process excludes already processed changes, applies ordered commits to the release branch, and labels completed pull requests.

Do I need GitHub CLI to backport pull requests to a release branch?▼

Yes, GitHub CLI operations are required to backport pull requests to a release branch. The workflow depends on GitHub CLI to retrieve merge commits, execute ordered cherry-pick operations, and create pull requests for the release branch.

How are cherry-pick conflicts handled when preparing a software release?▼

Handling cherry-pick conflicts when preparing a software release is part of the guided automated workflow. The process assists with branch setup, commit retrieval, ordered cherry-picking execution, conflict handling, and final release pull request creation.

Can I exclude already processed pull requests when collecting changes for a release version?▼

Yes, you can exclude already processed pull requests when collecting changes for a release version. The selection process specifically finds merged pull requests with the correct cherry-pick labels while automatically excluding changes that have already been processed.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
aliciaplsaliciapls

deployment-git

Coordinate Git workflows and PyPI publishing for Python SDK releases.

Community
Advanced
anevjesanevjes

github-operations

Automate GitHub branch, issue, pull request, and release workflows via gh CLI and MCP tools.

Community
Intermediate
aslakknutsenaslakknutsen

cherry-pick-backport

Backport upstream commits into downstream release branches with cherry-pick and conflict resolution.

Community
Advanced