Yicong-Huang opened a new pull request, #5978:
URL: https://github.com/apache/texera/pull/5978

   ### What changes were proposed in this PR?
   
   Collapse the labeler's two overlapping `bin/`-related labels into one.
   
   ```yaml
   # Before
   dev:   bin/**                                            ← no CI 
(informational only)
   infra: bin/local-dev*, bin/local-dev/**, bin/licensing   ← drives infra CI 
stack
   
   # After
   infra: bin/**                                            ← drives infra CI 
stack
   ```
   
   `dev` never triggered a CI job (not in `LABEL_STACKS`). The split meant PRs 
touching `bin/` outside the narrow infra glob (e.g. recent dead-code cleanup 
#5971 / #5973 deleting `bin/deploy-*`, `bin/server.sh`, the per-service 
wrappers) shipped without any of the lightweight infra smoke / unit tests 
running. PRs touching `bin/local-dev*` got both labels — `dev` was redundant.
   
   After this PR every change under `bin/` lights up the `infra` job, which is 
already cheap: no docker, no sbt, no live stack — just `find bin/**/test_*.sh` 
+ `pytest bin/`. As more tooling test suites land under `bin/<svc>/tests/` they 
pick up automatically.
   
   Also drops the two prose `dev` references in `required-checks.yml` (the 
precheck comment + the label/stack matrix's `docs / dev / deps / release/*` 
row).
   
   ### Any related issues, documentation, discussions?
   
   Closes #5977.
   
   ### How was this PR tested?
   
   Static. Confirmed:
   
   * `grep -rn` for the `dev` label across `.github/` returns nothing 
label-related — the remaining hits are `dev/bench` (benchmark data path) and 
`[email protected]` (mailing list).
   * The labeler's only other `bin/` glob (`infra:`) is now the canonical one.
   * `required-checks.yml`'s `LABEL_STACKS` already had `infra: ["infra"]` from 
#5961, so no map change needed.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Anthropic, 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]

Reply via email to