process-cherry-picks

Automating cherry-pick extraction involves parsing structured entries from tracker issue comments and organizing them into release notes worksheets and a cherrypicks file. This Skill validates issue titles and PR merge status via GraphQL to update worksheets and documentation accordingly.

When processing release notes worksheets, reverts are automatically removed from both done and todo worksheets. The system keeps only verified merged cherry-picks, ensuring the final cherrypicks.md file and worksheets reflect accurate release states.

Yes, PR merge status verification via GraphQL is supported before updating the cherrypicks file. The Skill checks release-branch PR merge status to validate issue titles and ensure only merged cherry-picks are appended to worksheets and documentation.

The best way to categorize cherry-pick entries by area is to append parsed entries to cherrypicks.md, grouped by category and area. This Skill automates that grouping by parsing tracker issue comments and organizing merged cherry-picks into structured release notes worksheets.

Yes, a specific tracker issue URL and version number are required inputs to start parsing cherry-picks. Running the process with these parameters triggers extraction, merge status validation via GraphQL, and worksheet updates for the specified PyTorch release.

Reverted cherry-picks are intentionally removed from done and todo worksheets during processing. The Skill filters out reverts and retains only merged cherry-picks validated via GraphQL, ensuring release notes worksheets and the cherrypicks list remain accurate.