Quick Notes205 words
Pipeline trigger rules — quick notes
Trigger rules — quick notes
| Fact | Detail |
|---|---|
Omitted CI trigger | Pushes to all branches when Disable implied YAML CI trigger is off and no UI override applies |
Omitted YAML pr | GitHub/Bitbucket Cloud: PRs to any branch when no UI override applies |
| Azure Repos PR validation | Branch-policy build validation, not YAML pr |
| Disable | trigger: none; GitHub/Bitbucket Cloud YAML PR: pr: none |
| Implied-trigger control | Organization/project setting; affects only an omitted trigger |
| Explicit-YAML override | Pipeline Override the YAML trigger from here setting |
| include vs exclude | exclude wins |
batch: true | Collect commits during a run; one run after, not one per push |
always: false (default) | Run only after source-code or pipeline-settings change since the last successful scheduled run |
| cron timezone | UTC |
| UI schedules | Take precedence over YAML schedules |
Traps
- Omitted triggers are not universally on: CI has setting conditions and YAML PR behavior is provider-specific.
- A branch in both include and exclude is excluded.
always: trueis required for nightly scans that must run on a quiet repo.