GitHub Actions allows people who use your GitHub Enterprise Server instance to improve productivity by automating every phase of the software development workflow.
|Automatically test and build your application
|"About continuous integration"
|Deploy your application
|"About continuous deployment"
|Automatically and securely package code into artifacts and containers
|"About packaging with GitHub Actions"
|Automate your project management tasks
|"Using GitHub Actions for project management"
GitHub Actions helps your team work faster at scale. When large repositories start using GitHub Actions, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "Writing and shipping code faster" in the State of the Octoverse.
You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. You can restrict your developers to using actions that exist on your GitHub Enterprise Server instance, or you can allow your developers to access actions on GitHub.com. For more information, see "About using actions in your enterprise."
GitHub Actions is developer friendly, because it's integrated directly into the familiar GitHub Enterprise Server experience.
You can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see "About self-hosted runners."
GitHub Actions provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.
GitHub Actions also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "Enforcing policies for GitHub Actions in your enterprise."
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."
GitHub Actions is not enabled for GitHub Enterprise Server by default. After you finish planning, you can follow the instructions for enabling GitHub Actions. For example, you may need to upgrade the CPU and memory resources for your GitHub Enterprise Server instance. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."