Skip to content

Disable Azure Pipelines PR validation (PR testing moved to GitHub Actions)#1742

Draft
jevansaks wants to merge 1 commit into
mainfrom
user/jevansa/disable-ado-pr-trigger
Draft

Disable Azure Pipelines PR validation (PR testing moved to GitHub Actions)#1742
jevansaks wants to merge 1 commit into
mainfrom
user/jevansa/disable-ado-pr-trigger

Conversation

@jevansaks

Copy link
Copy Markdown
Member

Summary

The azure-public microsoft.CsWin32 pipeline (azure-pipelines.yml) has a trigger: (CI) block but no pr: block. For GitHub-backed YAML pipelines, Azure DevOps enables PR validation by default when pr: is omitted, so it keeps queuing a build and posting a microsoft.CsWin32 status check on every pull request.

PR testing has moved to GitHub Actions (.github/workflows/build.yml), which runs more of the test matrix and works on forks. This sets pr: none so the Azure Pipelines pipeline no longer builds PRs.

Effect

  • ❌ No more Azure Pipelines PR builds / status checks on GitHub PRs.
  • ✅ CI on main, v*.*, and validate/* is unchanged (the trigger: block above is untouched).
  • ✅ Official/release/VS-insertion builds are unaffected.

Note on timing

Azure DevOps evaluates PR triggers from the YAML in the target branch (main), so pr: none takes effect for PRs opened after this merges. To silence in-flight PRs immediately, disable PR validation in the pipeline's Triggers UI (Override the YAML pull request trigger from here → Disable pull request validation).

…ions)

The azure-public 'microsoft.CsWin32' pipeline (azure-pipelines.yml) has no 'pr:' block, so Azure DevOps enables GitHub PR validation by default and keeps queuing a build / posting a status check on every PR. PR testing has moved to GitHub Actions (.github/workflows/build.yml), which runs more of the test matrix and works on forks. Set 'pr: none' so this pipeline no longer builds PRs; CI on main/v*/validate and release builds are unaffected.

Co-authored-by: Copilot <223556219+Copilot@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.

1 participant