Skip to main content

About GitHub Actions for enterprises

GitHub Actions can improve developer productivity by automating your enterprise's software development cycle.

About GitHub Actions for enterprises

GitHub Actionsを使うと、GitHub Enterprise Serverインスタンスを使う人はソフトウェアの開発ワークフローのすべてのフェーズを自動化することによって、生産性を改善できます。

TaskMore information
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 GitHub Enterprise Serverインスタンス, 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. If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "About security hardening with OpenID Connect."

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."

About getting started with GitHub Actions

始める前に、EnterpriseへGitHub Actionsをどのように導入するかを計画する必要があります。 詳しい情報については「EnterpriseへのGitHub Actionsの導入」を参照してください。

Enterpriseを他のプロバイダからGitHub Actionsに移行しているなら、追加で考慮すべきことがあります。 詳しい情報については「Enterpriseの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 GitHub Enterprise Serverインスタンス. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."

Further reading