GitHub Cherry Pick Assistant

Tracking since Apr 14, 2026.

Changelog

• May 20, 2026
  description

  # 🚀 GitHub Cherry Pick Assistant
  
  **GitHub Cherry Pick Assistant** helps engineering teams move pull request changes into the correct **target branch or repository** with less manual effort and better execution visibility.
  
  Built as a **persistent side panel inside GitHub**, the extension simplifies common **backporting and promotion workflows** by guiding developers through selecting a source PR, reviewing commits, choosing a target branch, and automatically creating a follow-up pull request.
  
  Instead of switching tools or running manual commands, developers can complete the entire cherry-pick workflow **directly inside GitHub**.
  
  ---
  
  # ✨ Key Features
  
  ### 🔐 GitHub Authentication
  
  Sign in securely using GitHub to access repositories and pull requests directly from the extension.
  
  ### 📥 Source Pull Request Selection
  
  Choose the repository and pull request that contains the commits you want to cherry-pick.
  
  ### 🎯 Target Repository & Branch Selection
  
  Select the destination repository and branch where the changes should be applied.
  
  ### 🧾 Commit-Level Control
  
  Review and select specific commits from the pull request before executing the cherry-pick.
  
  ### 🧠 Duplicate Commit Detection
  
  Automatically detect commits that already exist in the target branch to prevent duplication.
  
  ### ⚙️ Automated Cherry-Pick Execution
  
  Dispatch a **GitHub Actions workflow** to perform the cherry-pick automatically.
  
  ### 📊 Workflow Monitoring
  
  Track the progress and status of the workflow execution directly from the side panel.
  
  ### ⚠️ Conflict & Failure Insights
  
  Quickly view summaries of conflicts or failures to understand what needs manual intervention.
  
  ### 🔗 Follow-Up Pull Request Creation
  
  Once the cherry-pick succeeds, instantly open the generated pull request in the target repository.
  
  ---
  
  # 🧩 How It Works
  
  1️⃣ **Sign in with GitHub**
  2️⃣ **Select the source repository & pull request**
  3️⃣ **Review and choose commits**
  4️⃣ **Choose the target repository & branch**
  5️⃣ **Execute cherry-pick via GitHub Actions**
  6️⃣ **Monitor workflow progress**
  7️⃣ **Open the generated follow-up pull request**
  
  ---
  
  # 💡 Common Use Cases
  
  ### 🛠 Backporting Fixes
  
  Move bug fixes from `main` into release branches such as `release/1.2`.
  
  ### 🚀 Promoting Changes
  
  Promote approved changes from **staging/testing repositories to production repositories**.
  
  ### 🎯 Selective Commit Transfers
  
  Cherry-pick only specific commits from a pull request into another branch.
  
  ### 📦 Standardized Release Workflows
  
  Automate repetitive maintenance workflows across multiple repositories.
  
  ---
  
  # ❗ The Problem
  
  Cherry-picking across repositories or branches is often **manual, repetitive, and error-prone**.
  
  Developers usually have to:
  
  * Copy commit hashes manually
  * Switch repositories and branches
  * Create temporary branches
  * Run cherry-pick commands locally
  * Push changes manually
  * Create follow-up pull requests
  * Track failures or conflicts manually
  
  This process breaks developer flow and increases the risk of mistakes.
  
  ---
  
  # ✅ The Solution
  
  **GitHub Cherry Pick Assistant transforms cherry-picking into a structured workflow directly inside GitHub.**
  
  Teams can:
  
  ✔ Reduce manual work
  ✔ Improve consistency across releases
  ✔ Track execution status clearly
  ✔ Avoid duplicate commits
  ✔ Maintain visibility into workflow outcomes
  
  All without leaving the **pull request context**.
  
  ---
  
  # 🏢 Ideal For Teams That
  
  * Maintain **release branches**
  * Manage **production promotion pipelines**
  * Work with **multi-repository architectures**
  * Frequently perform **backports**
  * Want **reliable CI/CD-driven workflows**

  🚀 GitHub Cherry Pick Assistant
  
  GitHub Cherry Pick Assistant helps engineering teams move pull request changes into the correct target branch or repository with less manual effort and better execution visibility.
  
  Built as a persistent side panel inside GitHub, the extension simplifies common backporting and promotion workflows by guiding developers through selecting a source PR, reviewing commits, choosing a target branch, and automatically creating a follow-up pull request.
  
  Instead of switching tools or running manual commands, developers can complete the entire cherry-pick workflow directly inside GitHub.
  
  
  ✨ Key Features
  
  🔐 GitHub Authentication
  
  Sign in securely using GitHub to access repositories and pull requests directly from the extension.
  
  📥 Source Pull Request Selection
  
  Choose the repository and pull request that contains the commits you want to cherry-pick.
  
  🎯 Target Repository & Branch Selection
  
  Select the destination repository and branch where the changes should be applied.
  
  🧾 Commit-Level Control
  
  Review and select specific commits from the pull request before executing the cherry-pick.
  
  🧠 Duplicate Commit Detection
  
  Automatically detect commits that already exist in the target branch to prevent duplication.
  
  ⚙️ Automated Cherry-Pick Execution
  
  Dispatch a GitHub Actions workflow to perform the cherry-pick automatically.
  
  📊 Workflow Monitoring
  
  Track the progress and status of the workflow execution directly from the side panel.
  
  ⚠️ Conflict & Failure Insights
  
  Quickly view summaries of conflicts or failures to understand what needs manual intervention.
  
  🔗 Follow-Up Pull Request Creation
  
  Once the cherry-pick succeeds, instantly open the generated pull request in the target repository.
  
  🧩 How It Works
  
  1️⃣ Sign in with GitHub
  2️⃣ Select the source repository & pull request
  3️⃣ Review and choose commits
  4️⃣ Choose the target repository & branch
  5️⃣ Execute cherry-pick via GitHub Actions
  6️⃣ Monitor workflow progress
  7️⃣ Open the generated follow-up pull request
  
  💡 Common Use Cases
  
  🛠 Backporting Fixes
  
  Move bug fixes from `main` into release branches such as `release/1.2`.
  
  🚀 Promoting Changes
  
  Promote approved changes from staging/testing repositories to production repositories.
  
  🎯 Selective Commit Transfers
  
  Cherry-pick only specific commits from a pull request into another branch.
  
  📦 Standardized Release Workflows
  
  Automate repetitive maintenance workflows across multiple repositories.
  
  ❗ The Problem
  
  Cherry-picking across repositories or branches is often manual, repetitive, and error-prone.
  
  Developers usually have to:
  
  1. Copy commit hashes manually
  2. Switch repositories and branches
  3. Create temporary branches
  4. Run cherry-pick commands locally
  5. Push changes manually
  6. Create follow-up pull requests
  7. Track failures or conflicts manually
  
  This process breaks developer flow and increases the risk of mistakes.
  
  ✅ The Solution
  
  GitHub Cherry Pick Assistant transforms cherry-picking into a structured workflow directly inside GitHub.
  
  Teams can:
  
  ✔ Reduce manual work
  ✔ Improve consistency across releases
  ✔ Track execution status clearly
  ✔ Avoid duplicate commits
  ✔ Maintain visibility into workflow outcomes
  
  All without leaving the pull request context.
  
  
  🏢 Ideal For Teams That
  
  Maintain release branches
  Manage production promotion pipelines
  Work with multi-repository architectures
  Frequently perform backports
  Want reliable CI/CD-driven workflows

Permissions & access

Permissions

storageactiveTabsidePanelidentity

Host access

https://api.github.com/*, https://github-ext-auth-broker.aryanat1911.workers.dev/*

Screenshots