Move operator-init exemptions list to generated/#70361
Closed
shahar1 wants to merge 4 commits into
Closed
Conversation
…test The operator-init exemptions list lives under scripts/, so every PR that fixes an operator and drops its line from the list gets a backport-to-v3-3-test label. Those removals track work that only happens on main and are never backported, so the label is pure noise for the release manager triaging the backport queue.
shahar1
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
July 24, 2026 06:48
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
The list lived under scripts/, which is one of the paths that earns a backport-to-v3-3-test label, so every PR that fixes an operator and drops its line was flagged for a backport that never applies — the burn-down only happens on main. Sitting next to known_airflow_exceptions.txt also puts the two prek allowlists in the same place.
shahar1
changed the title
Contributor
Author
|
I'll merge this PR once handling most of the open PRs in #70359 |
Contributor
Author
|
At this rate we'll get done with the changes even before we get his merged, closing for now - I'll handle the labels manually. |
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
1 participant
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.
validate_operators_init_exemptions.txtlived underscripts/, which is one of thepaths that earns a
backport-to-v3-3-testlabel. Every PR that moves template-fieldlogic out of an operator's
__init__and drops that operator's line from the listtherefore got flagged for a backport that never applies — the burn-down
(#70296) only ever happens on
main.Moving the file to
generated/fixes that without touching the labeller:generated/matches no rule in
boring-cyborg.yml. It also puts the two prek allowlists in thesame place, next to
known_airflow_exceptions.txt.The hook itself is unchanged apart from the path, which now comes from
AIRFLOW_ROOT_PATHlike the other prek scripts. The stale-exemption error messageprints the repo-relative path instead of the bare filename, since the file no longer
sits next to the script.
Verified:
prek run validate-operators-init --all-filespasses, and the loader stillreads all 80 exempted classes across 62 files from the new location.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines