5e9821e0e5
Co-authored-by: SiaraMist <siaramist@github.com> Co-authored-by: Usha N <n-usha@github.com> Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> Co-authored-by: Dylan Smith <dylanatsmith@github.com> Co-authored-by: Alexis Abril <alexisabril@github.com> Co-authored-by: Dylan Geraci <67774922+heavymachinery@users.noreply.github.com>
2 lines
696 B
Markdown
2 lines
696 B
Markdown
Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow{% ifversion actions-custom-deployment-protection-rules-beta %}, gate deployments with custom deployment protection rules{% endif %}, or limit access to secrets. For more information about creating environments, see "[AUTOTITLE](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
|