Before enabling GitHub Actions, make sure you have completed the following steps:
Create your Azure storage account for storing workflow artifacts. GitHub Actions stores its data as block blobs, and two storage account types are supported:
A general-purpose storage account (also known as
general-purpose v2) using the standard performance tier.
Warning: Using the premium performance tier with a general-purpose storage account is not supported. The standard performance tier must be selected when creating the storage account, and it cannot be changed later.
A BlockBlobStorage storage account, which uses the premium performance tier.
For more information on Azure storage account types and performance tiers, see the Azure documentation.
Review the hardware requirements for GitHub Actions. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."
TLS must be configured for your GitHub Enterprise Server instance's domain. For more information, see "Configuring TLS."
Note: We strongly recommend that you configure TLS on GitHub Enterprise Server with a certificate signed by a trusted authority. Although a self-signed certificate can work, extra configuration is required for your self-hosted runners, and it is not recommended for production environments.
If you have an HTTP Proxy Server configured on your GitHub Enterprise Server instance, you must add
127.0.0.1to the HTTP Proxy Exclusion list. For more information on changing your proxy settings, see "Configuring an outbound web proxy server."
- From an administrative account on GitHub Enterprise Server, click in the upper-right corner of any page.
- In the left sidebar, click Management Console.
- In the left sidebar, click Actions.
- Select Enable GitHub Actions.
- Under "Artifact & Log Storage", select Azure Blob Storage, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the Azure documentation.
- Under the left sidebar, click Save settings.
- Wait for the configuration run to complete.
After the configuration run has successfully completed, GitHub Actions will be enabled on your GitHub Enterprise Server instance. For your next steps, such as managing GitHub Actions access permissions and adding self-hosted runners, return to "Getting started with GitHub Actions for GitHub Enterprise Server."