Trigger APIView CI on PRs when Azure.ClientSdk.Analyzers changes #13787
+1
−0
Conversation
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
…lyzers changes Co-authored-by: m-nash <[email protected]>
Co-authored-by: m-nash <[email protected]>
…etes Co-authored-by: m-nash <[email protected]>
Copilot
AI
changed the title
[WIP] Update CI to verify ApiView builds with Azure.ClientSdk.Analyzers
Add APIView build verification to Azure.ClientSdk.Analyzers CI
Jan 30, 2026
m-nash
reviewed
Feb 4, 2026
Co-authored-by: m-nash <[email protected]>
Copilot
AI
changed the title
Add APIView build verification to Azure.ClientSdk.Analyzers CI
Trigger APIView CI when Azure.ClientSdk.Analyzers changes
Feb 4, 2026
m-nash
reviewed
Feb 4, 2026
Co-authored-by: m-nash <[email protected]>
Copilot
AI
changed the title
Trigger APIView CI when Azure.ClientSdk.Analyzers changes
Trigger APIView CI on PRs when Azure.ClientSdk.Analyzers changes
Feb 4, 2026
m-nash
requested review from
helen229,
maririos and
praveenkuttappan
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
Updates APIView’s Azure Pipelines configuration so that pull requests modifying Azure.ClientSdk.Analyzers also trigger the APIView CI, ensuring APIView continues to build against analyzer changes before merge.
Changes:
- Added
src/dotnet/Azure.ClientSdk.Analyzersto the PR path filters insrc/dotnet/APIView/apiview.yml(without changing main-branch triggers).
jsquire
approved these changes
Feb 4, 2026
Member
|
/check-enforcer override |
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.
APIView depends on Azure.ClientSdk.Analyzers via ProjectReference but changes to the analyzers aren't verified against APIView before merge.
Changes
src/dotnet/Azure.ClientSdk.Analyzersto the pr path filters insrc/dotnet/APIView/apiview.ymlWhen PRs are created that modify Azure.ClientSdk.Analyzers, the APIView CI will automatically trigger. The APIView CI already builds the APIView project, which has a ProjectReference dependency on Azure.ClientSdk.Analyzers, so any breaking changes to the analyzers will be caught during the APIView build process before the PR is merged.
Note: The path is only added to PR triggers, not to regular triggers, to prevent unnecessary CI runs on direct commits to main while still providing verification during the PR review process.
Warning
<issue_title>Update CI for Azure.ClientSdk.Analyzers to verify that ApiView still builds</issue_title>
<issue_description>This project https://github.com/Azure/azure-sdk-tools/blob/main/src/dotnet/APIView/APIView/APIView.csproj depends on Azure.ClientSdk.Analyzers so we should verify it still builds when changing the analyzers in the CI.</issue_description>
Comments on the Issue (you are @copilot in this section)
<issue_title>Update CI for Azure.ClientSdk.Analyzers to verify that ApiView still builds</issue_title>
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.