How do permission scopes work when registering a new runner in a version control system?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do permission scopes work when registering a new runner in a version control system?
1 real search · 1 real-search pass
GitHub Actions self-hosted runner registration permissions scope repository organization runner groups official docs GitLab runner authentication token scope official docsGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
GitHub Actions self-hosted runner registration permissions scope repository organization runner groups official docs GitLab runner authentication token scope official docs Google ↗
- Self-hosted runners reference · docs.github.com
- REST API endpoints for self-hosted runner groups · docs.github.com
- REST API endpoints for self-hosted runners · docs.github.com
- Managing access to self-hosted runners using groups · docs.github.com
- Registering runners · docs.gitlab.com
- Access token scopes · docs.gitlab.com
- runner/docs/design/auth.md at main · actions/runner · github.com
Queries
1 queries · click a column to sort