This version of GitHub Enterprise was discontinued on 2021-09-23. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Using workflow templates

GitHub Enterprise Server provides workflow templates for a variety of languages and tooling.

Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.

Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.

About workflow templates

GitHub Enterprise Server offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, GitHub Enterprise Server analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use Node.js, GitHub Enterprise Server will suggest a template file that installs your Node.js packages and runs your tests.

You can also create your own workflow templates to share with your organization. For more information, see "Creating workflow templates."

Using workflow templates

Anyone with write permission to a repository can set up GitHub Actions workflows for CI/CD or other automation.

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.
  2. Under your repository name, click Actions. Actions tab in the main repository navigation
  3. If you already have a workflow in your repository, click New workflow.
  4. Find the template that you want to use, then click Set up this workflow.
  5. If the workflow template contains comments detailing additional setup steps, follow these steps.
  6. Some workflow templates use secrets. For example, ${{ secrets.npm_token }}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "Encrypted secrets."
  7. Optionally, make additional changes. For example, you might want to change the value of on to change when the workflow runs.
  8. Click Start commit.
  9. Write a commit message and decide whether to commit directly to the default branch or to open a pull request.

Further reading