Repository navigation
Use YAML to control pipeline triggers - #1353
Merged
Vladimir Morozov (vmoroz) merged 1 commit intoOct 17, 2026
Merged
Conversation
Danny van Velzen (dannyvv)
approved these changes
Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Why
Build the website when changes reach
main, and keep the pipeline activewithout relying on a schedule configured in the pipeline UI.
What
main, including merged PRs, build the website. PRbuilds stay disabled; the build does not deploy the website.
idle periods do not disable the pipeline.
Screenshots
Not applicable.
Testing
The edited entry file passes Azure Pipelines preview, including its expanded
trigger and monthly schedule.
Microsoft Reviewers: Open in CodeFlow