shahar1 opened a new pull request, #70361:
URL: https://github.com/apache/airflow/pull/70361

   `scripts/ci/prek/validate_operators_init_exemptions.txt` sits under 
`scripts/`, so
   every PR that moves template-field logic out of an operator's `__init__` and 
drops
   that operator's line from the exemptions list picks up a 
`backport-to-v3-3-test`
   label. Those removals only ever happen on `main` and are never backported, 
so the
   label is noise in the release manager's backport queue.
   
   The label rule now excludes that one file. `paths` follows gitignore 
semantics
   (boring-cyborg matches with the `ignore` package), which cannot re-include a 
file
   whose parent directory is excluded — hence the chain of directory 
re-includes down
   to the file rather than a single `!` line. A PR that touches the exemptions 
file
   *and* anything else in scope still gets labelled; only exemptions-only 
changes are
   skipped.
   
   `scripts/ci/prek/boring_cyborg.py` is updated to strip the leading `!` and 
trailing
   `/` before globbing, so the excluded paths are still validated to exist.
   
   Verified against `[email protected]` (the version boring-cyborg pins) with the 
committed
   config: exemptions-file-only PRs are not labelled, while `+ 
validate_operators_init.py`,
   `+ scripts/ci/docker-compose/base.yml`, `+ scripts/in_container/...`, `+ 
dev/...`,
   `+ .github/workflows/...` and `+ Dockerfile.ci` all still label as before.
   
   ---
   
   ##### 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]

Reply via email to