Yicong-Huang opened a new issue, #5977:
URL: https://github.com/apache/texera/issues/5977
### Task Summary
Today the labeler has two overlapping labels on `bin/`:
```yaml
dev: bin/** ← superset,
informational only
infra: bin/local-dev.sh, bin/local-dev-tui.py,
bin/local-dev/**, bin/licensing/** ← drives the infra
CI stack
```
`dev` is not in `LABEL_STACKS`, so it never triggers a CI job — it's purely
a triage tag. `infra` does drive the `infra` CI stack (which runs the
lightweight project-tooling unit + smoke tests added in #5961 / #5965).
The split is unhelpful in practice:
* A PR that edits `bin/server.sh` or `bin/deploy-*.sh` (anything under
`bin/` outside the narrow infra glob) gets `dev` but no CI — so dead-code
cleanup PRs like #5971 / #5973 ship without any verification.
* PRs that touch `bin/local-dev*` get *both* labels — `dev` is redundant.
* Reviewers have to know that `dev` does nothing while `infra` does — a
foot-gun.
Collapse the two:
* Drop the `dev:` rule entirely.
* Broaden `infra:` to `bin/**` so any change under `bin/` runs the infra CI
stack.
The infra job is cheap (no docker / sbt / live stack — just
`find`-discovered shell smoke + `pytest bin/`), so widening the scope is
essentially free. As we add more tooling test suites under `bin/<svc>/tests/`
they'll start running automatically.
Also drop the two prose references to the `dev` label in
`.github/workflows/required-checks.yml`'s precheck comment.
### Task Type
- [x] DevOps / Deployment / CI
- [x] Refactor / Cleanup
--
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]
