Choosing Runner Tags
This document introduces the tag types for AtomGit managed resource pools and self-hosted Runners, as well as two matching rules: full match and default equivalence.
When you need to precisely control on which type of Runner a job runs—specifying the operating system, architecture, resource specifications, or custom features (GPU, specific toolchains)—you need to understand the tag matching rules.
Configuration Description
Tag Type Mapping
| Runner Type | Tag Format | Example |
|---|---|---|
| AtomGit Managed Resource Pool | Three-part {os},{arch},{spec} or combined tags | [ubuntu-latest, x64, small] |
| AtomGit Managed Resource Pool (Default) | default | default (equivalent to [ubuntu-latest, x64, small]) |
| Self-Hosted | self-hosted + custom tags | [self-hosted, linux, gpu] |
Matching Rules
Rule One: Full Match
All tags in runs-on must simultaneously exist in the Runner's tag set to be considered a match.
# Runner tag set: {self-hosted, linux, x64, npu, cann}
# ✅ Match
runs-on: [self-hosted, linux, x64]
# ✅ Match
runs-on: [self-hosted, npu, cann]
# ❌ No match (tag set does not contain pypto)
runs-on: [self-hosted, pypto]
Rule Two: Default Equivalence
runs-on: default is equivalent to runs-on: [ubuntu-latest, x64, small].