[jenish0908]

Adds a boring-cyborg labeler rule that applies the kind:tests label when every file changed in a PR is a test file, for better stat collection.

closes: #61377

How it works

The rule uses a new allFilesMatch: true labeler option submitted to boring-cyborg in kaxil/boring-cyborg#133. Unlike the existing any-file-matches rules, it:

• adds the label only when all changed files match the test path globs (so it does not land on every PR that happens to touch a test, which was the problem with the first attempt in Add kind:tests label for PRs that only modify test files #61382),
• removes the label again if the PR later gains a non-test file (as discussed in Add kind:tests label for PRs that only modify test files #61382 review), and
• stays in sync on PR updates even though this repo sets labelOnPRUpdates: false, because it tracks the current state of the PR rather than suggesting an area.

The path list covers the tests/ directories of airflow-core, task-sdk, airflow-ctl, devel-common, providers and shared, plus the standalone test projects (airflow-ctl-tests, airflow-e2e-tests, task-sdk-integration-tests, kubernetes-tests, docker-tests). Happy to adjust the list per reviewer preference (e.g. whether Go/Java/TS SDK test files should count).

Merge-ordering dependency

⚠️ Please merge only after kaxil/boring-cyborg#133 is merged and the bot redeployed. The currently deployed bot would read this rule's paths but ignore the unknown allFilesMatch flag, i.e. it would apply kind:tests with the usual any-file-matches semantics — labeling every PR that touches a test file. With the updated bot the rule behaves as described above.

The kind:tests label does not exist yet; the GitHub API auto-creates it on first use, but a maintainer may prefer to create it upfront with a color/description matching the other kind:* labels.

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code

Generated-by: Claude Code following the guidelines

🤖 Generated with Claude Code

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.