A pipeline trigger is an event or condition that starts automation. For most pipelines, a source-code change in the repository should be the primary trigger; scheduled builds can supplement this, while cross-repository pipeline chaining usually signals unhealthy coupling. section 6.3.7
Configure triggers to make pipeline behavior predictable:
- Use repository changes as the default event, including tag creation where appropriate. section 6.3.7
- Apply branch and tag filters when only particular changes should run a job. section 6.3.7
- Reuse shared trigger conditions with YAML anchors instead of duplicating configuration. section 6.3.7
Run a job only for pushes to main
Define a reusable filter that permits the main branch and ignores tags, then attach it to the workflow job. This keeps the trigger explicit while allowing multiple jobs to share the same condition. section 6.3.7
