Skip to content

Conversation

@jairmyree
Copy link
Member

@jairmyree jairmyree commented Aug 26, 2025

This PR updates the new command documentation to reflect the migrated repo structure. This PR is not a comprehensive documentation update and other references to the old structure need to be updated as well. This PR is to unblock using the new-command.md to create new tools.

Copilot AI review requested due to automatic review settings August 26, 2025 21:53
@jairmyree jairmyree requested a review from a team as a code owner August 26, 2025 21:53
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the new command documentation to reflect the migrated repository structure, specifically changing references from the old areas/{area-name} directory structure to the new tools/Azure.Mcp.Tools.{AreaName} structure and updating project references from AzureMcp.Cli to Azure.Mcp.Server.

Key Changes:

  • Updates directory paths from areas/{area-name} to tools/Azure.Mcp.Tools.{AreaName} throughout documentation
  • Changes project references from AzureMcp.Cli to Azure.Mcp.Server
  • Updates namespace and class naming conventions from AzureMcp.{Area} to Azure.Mcp.Tools.{AreaName}

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
eng/scripts/Test-Code.ps1 Updates project paths and pattern matching for the new repository structure
eng/scripts/Deploy-TestResources.ps1 Changes test resources directory path to use new tools structure
docs/new-command.md Comprehensive documentation update reflecting all path, namespace, and project reference changes

@jairmyree
Copy link
Member Author

Due to this PR: #68, I'll remove updates to the test-deployment within this PR.

@jairmyree
Copy link
Member Author

@hallipr and I spoke about what to rename "Areas" to within the documentation. In the repo directory "areas" has been replaced with "Tools", but since we also refer to MCP commands as individual tools this creates ambiguity in documentation.

So far, we have decided to go with "toolset" in documentation that was previously referring to Areas.

…ture and documentation change of Area name to Toolset
@jairmyree jairmyree force-pushed the update-new_command-doc branch from dd0394c to 2092023 Compare August 29, 2025 17:31
jairmyree and others added 4 commits September 2, 2025 10:58
Co-authored-by: Alan Zimmer <[email protected]>
Co-authored-by: Alan Zimmer <[email protected]>
Co-authored-by: Patrick Hallisey <[email protected]>
Co-authored-by: Alan Zimmer <[email protected]>
@jairmyree jairmyree moved this to In Progress in Azure MCP Server Sep 2, 2025
@jairmyree jairmyree self-assigned this Sep 2, 2025
@jairmyree jairmyree merged commit 87bc5d2 into microsoft:main Sep 3, 2025
25 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Azure MCP Server Sep 3, 2025
feiskyer pushed a commit to feiskyer/microsoft-mcp that referenced this pull request Sep 8, 2025
colbytimm pushed a commit to colbytimm/microsoft-mcp that referenced this pull request Sep 27, 2025
…rosoft#63)

* Updating new-command.md and Program.cs to reflect new directory structure and documentation change of Area name to Toolset

* Updating cspell.json

* Update docs/new-command.md

Co-authored-by: Alan Zimmer <[email protected]>

* Update docs/new-command.md

Co-authored-by: Alan Zimmer <[email protected]>

* Update docs/new-command.md

Co-authored-by: Patrick Hallisey <[email protected]>

* Update docs/new-command.md

Co-authored-by: Alan Zimmer <[email protected]>

* Updating new-command and removing changes to Program.cs

---------

Co-authored-by: Alan Zimmer <[email protected]>
Co-authored-by: Patrick Hallisey <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants