sglang-cherrypick

Automate batch cherry-picking of merged PRs onto a release branch via GitHub Actions.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/annealing-inversion/sglang-kimi-deferral --skill sglang-cherrypick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sglang-cherrypick
Source: https://github.com/annealing-inversion/sglang-kimi-deferral/tree/main/.claude/skills/sglang-cherrypick
Command: npx skills add https://github.com/annealing-inversion/sglang-kimi-deferral --skill sglang-cherrypick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the batch cherry-pick of a set of merged PRs onto a release branch and provides per-PR visibility by reporting success/failure with links to the created cherry-pick PRs.

Core Features & Use Cases

  • Automatically dispatches the bot-cherry-pick workflow for each PR in the batch and ensures all target PRs reference the correct release branch.
  • Monitors each run to completion and reports per-PR results with direct links to the cherry-pick PRs (or the failure reason).
  • Performs pre-flight argument validation and conflict checks to catch issues before dispatch.

Quick Start

Provide the target release branch and one or more merged PR numbers to cherry-pick; the skill will validate inputs, dispatch workflows, and report results.

Frequently Asked Questions about sglang-cherrypick

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

FAQPage Schema
How do I automate cherry-picking multiple merged PRs to a GitHub release branch?

Automating batch cherry-picks of merged PRs to a release branch is handled by dispatching the bot-cherry-pick workflow for each PR, monitoring runs to completion, and reporting per-PR success or failure with direct links to the created cherry-pick PRs.

How do I check for git conflicts before cherry-picking a batch of PRs?

Pre-flight conflict checks for batch cherry-picking use git merge-tree validation to catch potential issues before dispatching workflows, ensuring argument validation and conflict detection occur upfront to prevent failed cherry-pick runs.

Do I need gh and git access to use automated cherry-pick workflows for sglang?

Yes, automated cherry-pick workflow dispatching and run monitoring require both gh and git access to the sgl-project/sglang repository to dispatch bot-cherry-pick workflows and track per-PR outcomes via GitHub Actions.

Can I batch cherry-pick merged PRs onto a release branch and track each PR status?

Batch cherry-picking merged PRs onto a release branch dispatches workflows for each PR and monitors runs to completion, reporting per-PR results with direct links to cherry-pick PRs or failure reasons for full tracking visibility.

What happens if a cherry-pick fails during automated release branch batch processing?

When a cherry-pick fails during batch processing, the automation reports the specific failure reason per PR alongside successful outcomes, providing direct links to created cherry-pick PRs for completed runs and failure details for others.