actions / actions/actions-runner-controller
Expose registration-token API for Repo-level self-hosted runners within an Org
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
Expose a registration-token API endpoint to generate Repo-level, self-hosted runner tokens using PAT.
Why is this needed?
Currently, the registration-token API endpoint only provides token generation for Org-level runners. In large organizations, delegation is critical. Project teams with repo-level permissions must be able to execute and automate their workflows end-to-end without the need for org-level permissions, assistance from org-level administrators, or manual intervention. Right now, every time our self hosted runner needs to be restarted, we have to go into Repo Settings on the website to generate a new token manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the registration-token API integration and the runner configuration entry point. Confirm the GitHub API requirements for repository-level tokens using a PAT, then verify that token generation supports runner restarts without org-level permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100