Tune prepare-providers-documentation skill classification and changelog rules#69569
Merged
vincbeck merged 1 commit intoJul 8, 2026
Merged
Conversation
eladkal
approved these changes
Jul 7, 2026
Contributor
|
just a thought.. we may want to ask the skill to notify RM if it detected top level block comment in the changelog that was not under scoped version. |
13cf9b5 to
1a5d7ec
Compare
Contributor
Author
Updated :) |
seanghaeli
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve the AI-driven provider documentation skill based on lessons learned from the last release wave (#69486).
Two issues observed during that run:
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
miscinstead ofskip. Examples: Fix inconsistency between generated provider docs and pyproject.toml #68991 (fix provider docs vs pyproject.toml inconsistency) and Add explicit [tool.flit.sdist] sections to flit-based pyproject.tomls #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 asskip.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?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.