Yicong-Huang opened a new pull request, #4654:
URL: https://github.com/apache/texera/pull/4654
### What changes were proposed in this PR?
Extend the `service` rule in `.github/labeler.yml` to also match these
root-level scala build / lint config files:
- `build.sbt` (root)
- `project/**` (sbt build sources, `plugins.sbt`)
- `.scalafix.conf` (moved to root by #3888)
- `.scalafmt.conf`
Today these files only match `**/build.sbt` (so they get the `dependencies`
label, which `LABEL_STACKS` from #4640 maps to no-op) or no rule at all
(`.scalafix.conf` / `.scalafmt.conf`). A PR that only edits one of them
therefore skipped the scala stack even though the change is purely a scala
build/lint setting — concrete example: PR #4649, which had labels
`dependencies, fix, frontend, release/v1.1.0-incubating` and union {frontend}
only, missing scala.
`service` already maps to the scala stack in `LABEL_STACKS`, so adding these
files there is enough — the union picks up scala automatically.
### Any related issues, documentation, discussions?
Closes #4653.
### How was this PR tested?
This PR's own labeler run will assign `service` (because
`.github/labeler.yml` is under `.github/workflows/**`? No — labeler.yml itself
only matches the `ci` rule via `.github/workflows/**`. So this PR will get `ci`
and run all stacks via the existing fan-out, which is fine for verification).
After merge, future PRs that only edit a root scala build file will pick up the
`service` label and run the scala stack.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7
--
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]
