6.4 KiB
title, shortTitle, intro, versions, type, topics
| title | shortTitle | intro | versions | type | topics | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| About GitHub Actions for enterprises | About GitHub Actions | {% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise's software development cycle. |
|
overview |
|
{% ifversion ghes < 3.3 %} {% note %}
Note: {% data reusables.enterprise.upgrade-ghes-for-actions %}
{% endnote %} {% endif %}
About {% data variables.product.prodname_actions %} for enterprises
{% data reusables.actions.about-actions-for-enterprises %}
| Task | More 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 {% data variables.product.prodname_actions %}" |
| Automate your project management tasks | "Using {% data variables.product.prodname_actions %} for project management" |
{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_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. {% ifversion ghec %}For more information, see "Finding and customizing actions."{% else %}You can restrict your developers to using actions that exist on {% data variables.product.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "About using actions in your enterprise."{% endif %}
{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} 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 {% ifversion ghec %}"About {% data variables.product.company_short %}-hosted runners" and{% endif %} "About self-hosted runners."
{% data variables.product.prodname_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.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} 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."{% endif %}
{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise."
About getting started with {% data variables.product.prodname_actions %}
{% data reusables.actions.introducing-enterprise %}
{% data reusables.actions.migrating-enterprise %}
{% ifversion ghes %} {% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. For more information, see "Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}."
{% else %} After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}."{% elsif ghae %}"Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}."{% endif %} {% endif %}
Further reading
- "Understanding {% data variables.product.prodname_actions %}"{% ifversion ghec %}
- "About billing for {% data variables.product.prodname_actions %}"{% endif %}