-
Notifications
You must be signed in to change notification settings - Fork 5.6k
update copilot instructions for tsp init and typespec doc retrieval #37361
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
Merged
chrisradek
merged 4 commits into
Azure:main
from
chrisradek:copilot-instructions-tsp-docs
Sep 15, 2025
Merged
update copilot instructions for tsp init and typespec doc retrieval #37361
chrisradek
merged 4 commits into
Azure:main
from
chrisradek:copilot-instructions-tsp-docs
Sep 15, 2025
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
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
maririos
reviewed
Sep 11, 2025
Member
Author
maririos
reviewed
Sep 15, 2025
|
|
||
| Before creating or initializing a TypeSpec project, you must know your org name, service name, and the type of service: data-plane or control-plane (ARM). | ||
|
|
||
| Then create a new project directory under the `specification/<orgName>/resource-manager/<RPNamespace>/<ServiceName>` or `specification/<orgName>/data-plane/<ServiceName>` path, following the guidelines below. |
Member
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.
maririos
reviewed
Sep 15, 2025
maririos
approved these changes
Sep 15, 2025
markcowl
pushed a commit
to markcowl/azure-rest-api-specs
that referenced
this pull request
Sep 18, 2025
…zure#37361) * update copilot instructions for tsp init and typespec doc retrieval * update typespec structure guidelines * missed unstaged change * fix formatting --------- Co-authored-by: Christopher Radek <[email protected]>
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.

This updates the copilot instructions to better support 2 scenarios:
init typespectool called when using a prompt like "Help me create a new Azure service using TypeSpec named Radek Trinkets". Including the structure guidelines helps copilot choose better directory names for the typespec project.