Skip to content

Limit Markdown-only CI exclusions to root files - #69149

Open
javiercn with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-ci-running-for-md-changes
Open

Limit Markdown-only CI exclusions to root files#69149
javiercn with Copilot wants to merge 3 commits into
mainfrom
copilot/fix-ci-running-for-md-changes

Conversation

Copilot AI commented Sep 8, 2026

Copy link
Copy Markdown
Contributor
  • You've read the Contributor Guide and Code of Conduct.
  • You've included unit or integration tests for your change, where applicable.
  • You've included inline docs for your change, where applicable.
  • There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Limit Markdown-only CI exclusions to repository-root files

Description

CI path filters

  • Replace recursive **/*.md exclusions with root-only *.md.
  • Keep documentation-only changes out of expensive CI while allowing nested AnalyzerReleases.*.md manifests to trigger validation.
- '*.md'

Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix CI legs running for .md file changes Limit Markdown-only CI exclusions to root files Sep 8, 2026
Copilot AI requested a review from javiercn September 8, 2026 17:57
@javiercn
javiercn marked this pull request as ready for review September 8, 2026 17:57
@javiercn
javiercn requested a review from wtgodbe as a code owner September 8, 2026 17:57
Copilot AI lite review requested due to automatic review settings September 8, 2026 17:57
@javiercn
javiercn requested a review from a team as a code owner September 8, 2026 17:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are small, consistent across the affected pipelines, and align with the stated goal of allowing nested Markdown (e.g., analyzer release manifests) to trigger validation.

Pull request overview

Updates Azure Pipelines PR path filters so that “Markdown-only” exclusions apply only to repository-root *.md files, allowing nested Markdown (notably AnalyzerReleases.*.md) to trigger the usual validation while still skipping expensive CI for root-doc-only PRs.

Changes:

  • Replaced PR path exclusions of **/*.md with *.md across several pipelines.
  • Updated the “report green” pipeline’s PR path includes to match the same root-only Markdown behavior.
  • Kept the rest of the doc/metadata path filtering behavior unchanged.
File summaries
File Description
.azure/pipelines/template-tests-pr.yml Limits Markdown exclusion to root *.md for template PR validation path filters.
.azure/pipelines/report-green.yml Limits Markdown-only “always green” triggering to root *.md.
.azure/pipelines/quarantined-pr.yml Limits Markdown exclusion to root *.md for quarantined PR validation path filters.
.azure/pipelines/components-e2e-tests.yml Limits Markdown exclusion to root *.md for Components E2E PR validation path filters.
.azure/pipelines/components-e2e-tests-internal.yml Limits Markdown exclusion to root *.md for internal Components E2E PR validation path filters.
.azure/pipelines/ci-public.yml Limits Markdown exclusion to root *.md for main public CI PR validation path filters.
Review details
  • Files reviewed: 6/6 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some CI legs are still running for .md changes

3 participants