![]() ![]() ![]() Some events have filters that give you more control over when your workflow should run.įor example, the push event has a branches filter that causes your workflow to run only when a push to a branch that matches the branches filter occurs, instead of when any push occurs. on: issues: types: - opened - labeledįor more information about each event and their activity types, see " Events that trigger workflows." Using filters If an issue with two labels is opened, three workflow runs will start: one for the issue opened event and two for the two issue labeled events. For example, the following workflow triggers when an issue is opened or labeled. If multiple triggering event activity types for your workflow occur at the same time, multiple workflow runs will be triggered. If you specify multiple activity types, only one of those event activity types needs to occur to trigger your workflow. If you specify the created activity type for the label event, your workflow will run when a label is created but not when a label is edited or deleted. If your workflow triggers on the label event, it will run whenever a label is created, edited, or deleted. Use on.types to define the type of event activity that will trigger a workflow run.įor example, the issue_comment event has the created, edited, and deleted activity types. Some events have activity types that give you more control over when your workflow should run. If multiple triggering events for your workflow occur at the same time, multiple workflow runs will be triggered. If you specify multiple events, only one of those events needs to occur to trigger your workflow. For example, a workflow with the following on value will run when a push is made to any branch in the repository or when someone forks the repository: on: You can specify a single event or multiple events. Using a single eventįor example, a workflow with the following on value will run when a push is made to any branch in the workflow's repository: on: push Using multiple events These options are described in the following sections. You can also restrict the execution of a workflow to only occur for specific files, tags, or branch changes. You can define single or multiple events that can a trigger workflow, or set a time schedule. For a list of available events, see " Events that trigger workflows." To automatically trigger a workflow, use on to define which events can cause the workflow to run. This value can include expressions and can reference the github and inputs contexts. For example, for a workflow triggered by a push or pull_request event, it is set as the commit message. If you omit run-name, the run name is set to event-specific information for the workflow run. GitHub displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. The name for workflow runs generated from the workflow. If you omit name, GitHub sets it to the workflow file path relative to the root of the repository. GitHub displays the names of your workflows on your repository's "Actions" tab. github/workflows directory of your repository. If you're new to YAML and want to learn more, see " Learn YAML in Y minutes." Workflow files use YAML syntax, and must have either a. ![]()
0 Comments
Leave a Reply. |