Skip to content

Split agent-service out of the service label #4642

@Yicong-Huang

Description

@Yicong-Huang

Task Summary

Split agent-service out of the broad service label so an agent-service-only PR runs only the agent-service CI stack, not the scala stack.

Context

Today the labeler's service rule matches every *-service/** directory, which includes both the scala-side services (access-control-service, config-service, file-service, computing-unit-managing-service, workflow-compiling-service, pyright-language-service) and agent-service. With the LABEL_STACKS map introduced in #4640, the service label maps to ["scala", "agent-service"], so any agent-service-only PR also triggers the full scala build.

Proposal

.github/labeler.yml:

  • Replace service's *-service/** glob with the enumerated scala-side service directories (actions/labeler@v6 does not support exclusion semantics in any-glob-to-any-file, so a !agent-service/** negation does not work).
  • Add a new agent-service label matching agent-service/**.

.github/workflows/required-checks.yml LABEL_STACKS:

service        -> { scala }
agent-service  -> { agent-service }

PRs that touch both stay covered: each label is applied independently and the run set is the union.

⚠️ Requires a repo admin to create the agent-service label in the repo before the labeler workflow can apply it (actions/labeler@v6 does not auto-create labels).

Priority

P2 – Medium

Task Type

  • Code Implementation
  • DevOps / Deployment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions