vLLM Ascend Release Note Writer

To generate release notes from GitHub commit history, fetch the commit diff between two version tags using a script to collect raw commits, categorize them in a CSV workspace by user impact, and draft structured highlights following project-specific inclusion criteria.

Structuring changelog sections involves categorizing analyzed commits into distinct groups like highlights, features, performance, dependencies, and breaking changes, then drafting a narrative that aligns with reference style headings to ensure reader-friendly release documentation.

Collect and analyze commits for a version release by running a fetch script to pull the commit delta between the previous and current tags, then triage each commit into a CSV file to decide its inclusion and category before drafting.

Yes, the release note drafting pipeline works with GitHub repositories by utilizing the gh command line tool and requests to pull commit diffs between tags, ensuring the collected raw data is grounded in actual repository history.

Release note output files are organized by version by saving all generated artifacts, including the highlights draft and edited final draft, under a dedicated directory structure like vllm-ascend-release-note/output/$version for consistent publishing.

Before drafting versioning documentation for vLLM Ascend, you need the dotenv and gh dependencies configured, access to the GitHub repository to fetch commit deltas, and the provided CSV workspace to categorize raw commits.