1
0
mirror of synced 2025-12-19 18:10:59 -05:00

[EDI] Triggering a workflow (#56663)

This commit is contained in:
Felix Guntrip
2025-07-16 20:01:53 +01:00
committed by GitHub
parent 9821ed8608
commit c0851f6966
2 changed files with 13 additions and 13 deletions

View File

@@ -18,21 +18,11 @@ redirect_from:
{% data reusables.actions.enterprise-github-hosted-runners %}
## About workflow triggers
## Prerequisites
{% data reusables.actions.about-triggers %}
To learn more about workflows and triggering workflows, see [AUTOTITLE](/actions/concepts/workflows-and-actions/workflows).
Workflow triggers are defined with the `on` key. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#on).
The following steps occur to trigger a workflow run:
1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
1. {% data variables.product.github %} searches the `.github/workflows` directory in the root of your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. When a workflow runs, {% data variables.product.github %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see [AUTOTITLE](/actions/learn-github-actions/variables).
### Triggering a workflow from a workflow
## Triggering a workflow from a workflow
{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication).

View File

@@ -6,3 +6,13 @@ Workflow triggers are events that cause a workflow to run. These events can be:
* Manual
For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.
Workflow triggers are defined with the `on` key. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#on).
The following steps occur to trigger a workflow run:
1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
1. {% data variables.product.github %} searches the `.github/workflows` directory in the root of your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. When a workflow runs, {% data variables.product.github %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see [AUTOTITLE](/actions/learn-github-actions/variables).