Summary
Your goal in this module was to identify the tools and strategies you can use in your GitHub Enterprise instance to manage the use of GitHub Actions in your organization.
To accomplish this goal, you learned how to:
- Use different tools at enterprise and organization levels to manage your actions and workflows.
- Evaluate what the appropriate runners are for your enterprise instance.
- Customize your self-hosted runners according to your enterprise use case.
- Scope, create, and access encrypted secrets in your actions and workflows.
Next, you practiced how to create an encrypted secret in a repository and pass it in an action.
Learn more
Here are some links to more information on the topics we discussed in this module:
- Creating a Docker container action
- Enabling automatic access to GitHub.com actions using GitHub Connect
- Enforcing policies for GitHub Actions in your enterprise
- Manually syncing actions from GitHub.com
- Sharing workflows, secrets, and runners with your organization
- Using secrets in GitHub Actions
- Metadata syntax for GitHub Actions
- Using GitHub-hosted runners
- About self-hosted runners
- Managing access to self-hosted runners using groups
- Using self-hosted runners in a workflow
- Using labels with self-hosted runners
- Using a proxy server with self-hosted runners
- Using GitHub Actions with an IP allowlist
- Monitoring and troubleshooting self-hosted runners
Provide feedback
Use this issue form to provide content feedback or suggested changes for this Microsoft Learn module. GitHub maintains this content and a team member will triage the request. Thank you for taking the time to improve our content!