staging-cherry-pick

To cherry-pick commits to a staging branch, this skill extracts non-merge commits from merged pull requests and applies them sequentially. It automates the git cherry-pick process to safely propagate specific features without pulling in merge commits.

Automated cherry-picking resolves CHANGELOG.md conflicts semantically by prioritizing existing staging branch entries. This ensures that changelog conflicts are handled cleanly and identified early during the release management process.

Yes, you need the GitHub CLI and Node.js to automate git cherry-picks. These dependencies are required to execute non-interactive git operations and query API data for extracting individual commits from merged pull requests.

You can selectively promote features by cherry-picking individual commits from merged pull requests. This skill specifically excludes merge commits, ensuring only the targeted feature changes are applied to the staging branch for release testing.

The best way to automate cherry-picking multiple PRs is providing a list of pull requests to this skill. It sequentially applies the extracted non-merge commits to the staging branch, managing changelog conflicts automatically throughout the process.