Yicong-Huang opened a new pull request, #4641: URL: https://github.com/apache/texera/pull/4641
### What changes were proposed in this PR? Stacked on #4640. Split `agent-service` out of the broad `service` label so an agent-service-only PR no longer drags in the scala stack. `.github/labeler.yml`: - Replace the catch-all `*-service/**` glob with the enumerated set of scala-side services (`access-control-service`, `computing-unit-managing-service`, `config-service`, `file-service`, `pyright-language-service`, `workflow-compiling-service`). - Add a new `agent-service` label matching `agent-service/**`. `.github/workflows/required-checks.yml`: ```js service: ["scala"], // was ["scala", "agent-service"] "agent-service": ["agent-service"], // new entry ``` Updated decision table: | label | frontend | scala | python | agent-service | |---|---|---|---|---| | `frontend` | ✓ | | | | | `python` | | ✓ | ✓ | | | `engine` | | ✓ | ✓ | | | `service` | | ✓ | | | | `agent-service` | | | | ✓ | | `common` | | ✓ | | | | `ddl-change` | | ✓ | | | | `ci` | ✓ | ✓ | ✓ | ✓ | | `docs` / `dev` / `dependencies` / `release/*` / branch-name | | | | | PRs that touch both directories keep both labels and run both stacks via the existing union. ### Any related issues, documentation, discussions? Stacked on #4640 (which introduces `LABEL_STACKS`). Refines the open question raised on #4639. ⚠️ **Repo admin action required before merge:** the `agent-service` label has to exist in the repository. `actions/labeler@v6` does not auto-create labels. ### How was this PR tested? To be exercised by this PR's own run: it touches `.github/workflows/**` and `.github/labeler.yml`, which gets the `ci` label, so every stack should run. After merge, an agent-service-only PR (e.g. an `agent-service/src/**` change) should run only the agent-service stack and skip frontend/scala/python. ### 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]
