Unverified50% confidenceFactExact time
GitLab uses a tag matching mechanism: a job declares the required tags in its configuration, and only Runners carrying those tags can pick up that job.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn the GitLab Jobs API, the `runner` field records the Runner that actually executed the Job and its tags, and is field-level evidence for identifying the "free server instead of Runner" misconception.72% similarVerifiedGit tags come in two types—lightweight tags and annotated tags—where annotated tags are complete objects in the Git database containing creator information, date, description, and an optional GPG signature.69% similarUnverifiedactions/checkout 的作用是将仓库代码检出到 GitHub Actions 的 Runner 环境中67% similarUnverifiedWhen Factory polls GitHub to check for tasks, it uses ordinary code to call the GitHub REST API to check for label changes, consuming no tokens, and only launches agents when there is actual work to do.67% similarUnverifiedworktree.guessRemote makes Git find the remote-tracking branch that uniquely matches the new branch name, check it out, and set its upstream, but it matches by folder basename, so names containing slashes cannot be matched.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1101541API
curl https://kongchang.com/api/v1/knowledge/claims/1101541MCP
get_claim(id=1101541)