docs: document missing pipeline filter options (branch, build-reason, expression)#530
Merged
jamesadevine merged 1 commit intoMay 13, 2026
Conversation
… expression) The on.pipeline.filters section in docs/front-matter.md and prompts/create-ado-agentic-workflow.md only showed source-pipeline and time-window as filter options. Three additional pipeline filter fields are fully implemented in PipelineFilters (src/compile/types.rs) and their lowering is documented in docs/filter-ir.md, but were absent from user-facing documentation: - branch: glob match on triggering branch (Build.SourceBranch) - build-reason: include/exclude by build reason (same as PR filters) - expression: raw ADO condition escape hatch Also clarifies in the filter validation table that build-reason validation applies to both PR filters and pipeline filters. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jamesadevine
approved these changes
May 13, 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
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.
Documentation Freshness Audit
This audit found the following inconsistency between code and documentation:
Findings
branch,build-reason, andexpressionfilter options are fully implemented inPipelineFiltersbut absent from user-facing examplesdocs/front-matter.md,prompts/create-ado-agentic-workflow.mdDetails
The
on.pipeline.filtersYAML examples in both user-facing docs only showedsource-pipelineandtime-window:Three additional fields on
PipelineFilters(src/compile/types.rs) are fully implemented and lowered bylower_pipeline_filters()insrc/compile/filter_ir.rs, and are referenced in the developer-focuseddocs/filter-ir.md— but were absent from user-facing examples:branch—GlobMatchon$(Build.SourceBranch)(TriggeringBranchfact). Useful for filtering pipeline-completion triggers to specific branches of the upstream pipeline.build-reason—include/excludeby build reason (same semantics as the PR filter variant). Already validated at compile time for conflicting include/exclude.expression— raw ADO condition escape hatch (same aspr.filters.expression, already documented in the Expression Escape Hatch section offront-matter.md).An AI agent authoring a pipeline using the
prompts/create-ado-agentic-workflow.mdprompt would have no way to discover these filter options.Applied Fixes
branch,build-reason, andexpressionto theon.pipeline.filtersYAML example indocs/front-matter.mdbranch,build-reason, andexpressionto Step 11's pipeline trigger filters example inprompts/create-ado-agentic-workflow.mdbuild-reasonconflict detection applies to both PR filters and pipeline filtersThis pull request was created by the automated documentation freshness check.