shahar1 opened a new pull request, #68755:
URL: https://github.com/apache/airflow/pull/68755

   When the release manager generates the provider testing issue
   (`breeze release-management generate-issue-content-providers`), new
   providers had no PR references in their changelog — the changelog only
   records changes made *after* the initial release — so their entry showed
   only a generic placeholder:
   
   > Initial release does not list PR references in changelog. Please run smoke 
tests.
   
   This made it hard for testers to know what actually went into a brand new
   provider.
   
   This PR makes new-provider entries list their related commits. For a new
   provider, the related PRs are collected directly from the git history of
   the provider's sources and rendered with the **same checkbox format**
   (PR title, number and author) used for existing providers. The
   `:tada: New provider` marker is retained, and a note is added warning that
   the list may include bootstrap and development commits (e.g.
   release-preparation commits) that are not user-facing changes. When git
   history yields no PRs, the entry still falls back to the smoke-test
   placeholder.
   
   Example output for `clickhousedb` (new provider):
   
   > ## Provider [clickhousedb: 1.0.0rc2](...) **:tada: New provider**
   >    > **Note:** This is a new provider, so the PRs below are collected from 
the git history of the provider's sources rather than from a changelog diff. 
The list may therefore include bootstrap and development commits (e.g. 
release-preparation commits) that are not user-facing changes.
   >    - [ ] [Add ClickHouse Provider (#67080)](...): @BentsiLeviav
   >    - ...
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.8)
   
   Generated-by: Claude Code (Opus 4.8) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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