Getting started with GitHub Actions for GitHub AE

Learn about configuring GitHub Actions on GitHub AE.

Site administrators can enable GitHub Actions and configure enterprise settings.

About GitHub Actions on GitHub AE

This article explains how site administrators can configure GitHub AE to use GitHub Actions.

GitHub Actions is enabled for GitHub AE by default. To get started using GitHub Actions within your enterprise, you need to manage access permissions for GitHub Actions and add runners to run workflows.

Before you get started, you should make a plan for how you'll introduce GitHub Actions to your enterprise. For more information, see "Introducing GitHub Actions to your enterprise."

If you're migrating your enterprise to GitHub Actions from another provider, there are additional considerations. For more information, see "Migrating your enterprise to GitHub Actions."

Managing access permissions for GitHub Actions in your enterprise

You can use policies to manage access to GitHub Actions. For more information, see "Enforcing GitHub Actions policies for your enterprise."

Adding runners

You can configure and host servers to run jobs for your enterprise on GitHub AE. Self-hosted runners allow you to host your own runners and customize the environment used to run jobs in your GitHub Actions workflows. For more information, see "Hosting your own runners."

General security hardening for GitHub Actions

If you want to learn more about security practices for GitHub Actions, see "Security hardening for GitHub Actions."

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.