Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions: Limit self-hosted Runners to specific workflows on GHES #255

Open
github-product-roadmap opened this issue Oct 8, 2021 · 0 comments

Comments

@github-product-roadmap
Copy link
Collaborator

@github-product-roadmap github-product-roadmap commented Oct 8, 2021

Summary

This feature enables organizations to limit self-hosted runners to specific workflows.

Intended Outcome

Many organizations with self-hosted runners store tokens on the runner machines, and want to ensure that only selected workflows have access to those tokens. This feature enables organizations to automate this requirement.

When used in combination with reusable workflows, this feature enables organizations to require that specific security and compliance steps are executed in order to perform sensitive tasks, such as deploying to production.

How will it work?

Organizations will be able to select which workflows can access a runner group through the UI and API. Workflows that haven’t been selected, and which attempt to use a runner in the restricted group, will fail with a descriptive error message.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
GitHub public roadmap
Q2 2022 – Apr-Jun
Status: Q2 2022 – Apr-Jun
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant