potiuk opened a new pull request, #69057: URL: https://github.com/apache/airflow/pull/69057
### Problem The `check-no-new-airflow-exceptions` hook keeps its allowlist baseline at `scripts/ci/prek/known_airflow_exceptions.txt`. That file is updated by **any** PR that legitimately adds, removes, or moves a `raise AirflowException` — typically provider or core changes with nothing to do with dev tooling. Because it lived under `scripts/`, boring-cyborg matched it against the `scripts/**/*` glob and auto-applied `area:dev-tools` and — the real problem — `backport-to-v3-3-test`, triggering **wrong automated backports** of unrelated provider PRs (e.g. the false backport flagged on #69019). ### Fix Move the generated allowlist to `generated/known_airflow_exceptions.txt`. No boring-cyborg rule matches `generated/`, so editing the baseline no longer looks like a dev-tools change and won't auto-label/backport. The hook script now reads/writes it from the repo-root `generated/` directory (via the existing `REPO_ROOT`). `.txt` files carry no license header (no `insert-license` hook covers `.txt`), so nothing else changes. Pure rename + 4 path-reference updates in the hook script; verified the hook still passes and `--generate` writes to the new location. > Worth backporting to `v3-3-test` so the same false trigger is fixed there. --- ##### 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]
