Step 1
Choose the source pull request
Start from the PR that contains the changes you want to move. The extension can infer context from the GitHub page or let you select it manually.
GitHub Cherry Pick Assistant
Workflow automation for GitHub teamsGitHub Side Panel Extension
Select a source pull request, choose the commits you need, target the correct repository and branch, and let GitHub Actions create the follow-up pull request for you.
Execution Preview
Side panel workflowChoose the pull request to promote or backport.
Select the exact commits to apply.
Pick the repository and branch that should receive the changes.
Launch GitHub Actions, track status, and open the follow-up pull request.
How It Works
The extension is designed to keep the workflow inside GitHub: you review the source, choose the target, and let GitHub Actions handle the actual git operations.
Step 1
Start from the PR that contains the changes you want to move. The extension can infer context from the GitHub page or let you select it manually.
Step 2
Inspect the commits in that pull request, select exactly what should move, and check for duplicates that already exist on the target branch.
Step 3
Choose where the changes should land, whether that is a release branch, a maintenance branch, or a different repository entirely.
Step 4
GitHub Actions performs the cherry-pick, pushes the branch, opens the follow-up PR, and reports conflicts or partial results back through the workflow.
Key Benefits
Use it for backports, promotions, and target-branch maintenance work without repeating the same manual Git steps every time.
Review and select only the commits you want instead of blindly moving an entire pull request.
Dispatch GitHub Actions, follow the workflow run, and inspect conflict summaries from the side panel.
Create the resulting pull request automatically after successful or partially successful execution.
Work across the same repository or a separate target repository depending on how your team promotes changes.
Install
Publish this extension to the Chrome Web Store or distribute the unpacked build inside your team. The current production auth broker is already configured for a public sign-in flow.