vincbeck opened a new pull request, #69569:
URL: https://github.com/apache/airflow/pull/69569
Improve the AI-driven provider documentation skill based on lessons learned
from the last release wave (#69486).
Two issues observed during that run:
1. PRs that only touch build tooling or breeze templates — with the
provider-scoped diff limited to regenerated files like README.rst or index.rst
— were classified as `misc` instead of `skip`. Examples: #68991 (fix provider
docs vs pyproject.toml inconsistency) and #65861 (add flit sdist sections). The
deterministic classifier doesn't catch these because it only looks at file
paths within the provider, not whether those files are template-generated
output. Added explicit guidance in both the sub-agent prompt and the Phase 3
notes so the LLM correctly classifies these as `skip`.
2. Some PR titles use Conventional Commit prefixes (`feat:`, `refactor:`,
etc.) which should not appear in changelogs. Added a rule in Phase 4b to strip
these prefixes before writing changelog entries.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.6)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
