shahar1 opened a new pull request, #68663:
URL: https://github.com/apache/airflow/pull/68663
The AI-driven `prepare-providers-documentation` skill instructed the release
manager to copy each commit subject verbatim into the changelog ("Subjects must
be the original commit subject ... Don't paraphrase"). In practice that
produced low-quality entries that reviewers had to fix by hand during the
2026-06-16 provider wave:
- uninformative wording (`Add missing template_fields to FooOperator`, `fix
the ftp tls`),
- Conventional-Commit / scope prefixes (`fix:`, `docs:`, `refactor:`,
`fix(test_wasb.py):`),
- lowercase starts and non-imperative mood (`made ... to run`, `Renaming
...`),
- raw dependency/dependabot phrasing instead of the actual version (`Bump
aiohttp regarding dependabot warning`),
- test-file references in user-facing notes,
- non-user-facing CI / JS build-tooling bumps surfaced in visible sections,
- providers released with no user-facing change.
This replaces the "don't paraphrase" rule with explicit **entry-wording
rules** (capitalized, imperative, no prefixes, specific, dependency bumps
pinned to the version read from `pyproject.toml`, Airflow-core compatibility
notes), a **"what is not user-facing → hidden block"** section (CI/infra bumps,
JS build/dev tooling, comment-only changes, internal renames), and an
instruction to **drop a provider to doc-only** (no release) when nothing
user-facing remains. It also extends the Phase 3 auto-classify heuristics so CI
and build-tooling bumps are classified `skip` up front.
Documentation/tooling-only change to the skill; no runtime Airflow code is
affected.
---
##### 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]
