-
Notifications
You must be signed in to change notification settings - Fork 271
Updating new-command documentation to reflect new repo structure #63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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}totools/Azure.Mcp.Tools.{AreaName}throughout documentation - Changes project references from
AzureMcp.ClitoAzure.Mcp.Server - Updates namespace and class naming conventions from
AzureMcp.{Area}toAzure.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 |
|
Due to this PR: #68, I'll remove updates to the test-deployment within this PR. |
|
@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
dd0394c to
2092023
Compare
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]>
…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]>
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.