Document multi-repo ownership boundaries - #55432
Merged
Merged
Conversation
Clarify component ownership, VMR code flow, dependency provenance, and cross-repository fix placement for SDK agents. Correct the Template Engine guidance now that its source is maintained in the SDK repository. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 99b4cd14-14dc-459c-bac7-f984c9d2632b
…cument-vmr-context
Qualify compiler ownership, document flowed version properties, and align direct VMR change guidance with current contribution boundaries. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 99b4cd14-14dc-459c-bac7-f984c9d2632b
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 99b4cd14-14dc-459c-bac7-f984c9d2632b
Remove redundant repository entries and keep the agent guidance focused on ownership boundaries that affect SDK issue routing. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 99b4cd14-14dc-459c-bac7-f984c9d2632b
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the agent-facing .github/copilot-instructions.md to more explicitly document cross-repository ownership boundaries and how the dotnet/dotnet VMR fits into investigations, helping contributors identify the correct upstream repo for SDK-visible behavior.
Changes:
- Replaces the prior “do not assume it belongs here” paragraph with a dedicated “Repository boundaries and the VMR” section.
- Adds an ownership-boundaries table mapping key sibling repos (runtime/roslyn/msbuild/nuget/project-system/dotnet) to the behaviors they own.
- Clarifies that diagnostics and generated code are not sufficient to infer ownership (e.g., analyzers/generators may be owned elsewhere).
Give dotnet/fsharp its own repository-boundary row and keep Roslyn ownership focused on C# and Visual Basic. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 99b4cd14-14dc-459c-bac7-f984c9d2632b
lbussell
approved these changes
Jul 23, 2026
45 tasks
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.
SDK-visible behavior is often implemented in sibling repositories. This guides agents to understand how all the components that get consolidated in the SDK and where to look when those components are involved in an investigation.
Contributes to #55185.