Skip to content

Latest commit

 

History

History
56 lines (39 loc) · 5.18 KB

File metadata and controls

56 lines (39 loc) · 5.18 KB
title shortTitle intro versions type topics redirect_from
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.
ghec ghes
*
*
overview
Actions
Enterprise
/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises

About {% data variables.product.prodname_actions %} for enterprises

{% data reusables.actions.about-actions-for-enterprises %}

Task More information
Automatically test and build your application AUTOTITLE
Deploy your application AUTOTITLE
Automatically and securely package code into artifacts and containers AUTOTITLE
Automate your project management tasks AUTOTITLE

{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, pull requests are typically merged faster, allowing teams to merge more pull requests per day.

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 AUTOTITLE.{% else %}You can restrict your developers to using actions that exist on {% data variables.location.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see AUTOTITLE.{% endif %}

{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.github %} 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 %}AUTOTITLE and{% endif %} AUTOTITLE.

{% 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. 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 AUTOTITLE.

{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see AUTOTITLE.

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.location.product_location %}. For more information, see AUTOTITLE.

{% 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 %}AUTOTITLE.{% endif %} {% endif %}

Further reading