Jens-G opened a new pull request, #3521:
URL: https://github.com/apache/thrift/pull/3521

   ## Summary
   
   - Adds `build/gen-changes.py` — a script that generates a `CHANGES.md` draft 
by combining git commit history, JIRA ticket summaries (via the public JIRA 
REST API), and GitHub PR metadata (labels and commit→PR resolution via the 
GitHub API)
   - Adds `.github/workflows/generate-changes.yml` — a CI job that runs the 
script on every push to `master` and `release/**` branches (upstream repo only) 
and on manual `workflow_dispatch` with an optional `jira_version` input; 
uploads the result as a 3-day build artifact named `changes-draft`
   - Adds a `.gitignore` exception for `build/gen-changes.py` (matched by the 
existing `gen-*` pattern intended for compiler output directories)
   
   ## How it works
   
   The script has three complementary data sources:
   
   1. **Git commits** (always): walks the range from the last `v*` tag to the 
branch tip, extracts `THRIFT-NNNN` references, and groups ticket-less commits 
by their `Client:` trailer
   2. **JIRA** (primary when `--jira-version` is given): queries all tickets 
with that `fixVersion` for the authoritative release list
   3. **GitHub PR labels** (fallback): for commits without a `Client:` trailer, 
fetches PR labels to determine the CHANGES.md section; with `--github-token`, 
also resolves commit→PR links for commits whose subject lacks the standard 
`(#NNN)` suffix
   
   ## Test plan
   
   - [ ] Run `python3 build/gen-changes.py` locally and review output
   - [ ] Run with `--github-token` to verify commit→PR link resolution and 
label fetching
   - [ ] Run with `--jira-version 0.24.0` to verify JIRA fixVersion query
   - [ ] Confirm `generate-changes` workflow appears in Actions and produces a 
downloadable artifact after merge
   
   🤖 Generated with [Claude Code](https://claude.ai/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to