Build what's next on GitHub, the place for anyone from anywhere to build anything.
Join us October 28-29 in San Francisco or online for GitHub Universe, our flagship developer event uniting people, agents, and the world's code.
Limit use of external actions within Actions workflow for enterprises, organizations, and repositories.
You can now fine-tune access to external actions. These updated settings make it easier to achieve your security and compliance goals with GitHub Actions.
GitHub authors a number of essential actions which are widely used, such as ‘checkout’. When you check the box for GitHub-authored actions, you’re allowing workflows to use any action in the GitHub organization or the actions organization, including those that will be created in the future.
You can also limit the community actions that can be executed to just those created by GitHub-verified authors. With GitHub-verified authors, GitHub ensures that the organization that created the action is authentic, and truly represents the company or entity which it appears to represent (GitHub does not review any code or security practices as part of its verification process). When you check the box for GitHub-verified authors, you’re allowing workflows to use any action in the verified author’s organization, including those that will be created in the future.
The most secure way to use GitHub Actions includes a review of the source code of all external actions. You can now ensure that workflows use only those actions that have been reviewed by creating an explicit allow list. You can use the * syntax to create flexible patterns. When you use the allow list, only actions that patch a pattern in the list are allowed.
The allow list for specific actions can be used for any public repository, or private repositories that are part of a GitHub Enterprise plan.
To get started with Actions policies, visit our documentation.
