Skip to content

Commit ddb15b4

Browse files
Update copilot instructions and prompts (#35443)
1 parent bf90cab commit ddb15b4

File tree

3 files changed

+5
-3
lines changed

3 files changed

+5
-3
lines changed

.github/copilot-instructions.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,7 @@ from the list of paths. If user does not have a TypeSpec project, then prompt us
156156

157157
### Pre-requisites
158158
- User should have a GitHub account and should be logged in to GitHub account using GitHub CLI `gh auth login`.
159+
- run `npm ci` to install the dependencies
159160

160161

161162
### Basic Rules for SDK Generation from TypeSpec

.github/prompts/create-release-plan.prompt.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ tools: ['CreateReleasePlan', 'GetReleasePlanForPullRequest', 'GetReleasePlan', '
44
---
55

66
# Release Plan Creation Process
7-
7+
You goal is to create a valid release plan. You must prompt user to provide all required information and all input must match the format and requirement mentioned in step 3 below.
88
Follow these steps in order to create or manage a release plan for an API specification pull request:
99

1010
## Step 1: Validate Prerequisites
@@ -30,7 +30,7 @@ If any details are missing, prompt the user accordingly:
3030
- GA (Generally Available)
3131
- **Service Tree ID**: GUID format identifier for the service in Service Tree. Before creating release plan, always show the value to user and ask them to confirm it's a valid value in service tree.
3232
- **Product Service Tree ID**: GUID format identifier for the product in Service Tree. Before creating release plan, always show the value to user and ask them to confirm it's a valid value in service tree.
33-
- **Expected Release Timeline**: Format as "Month YYYY" (e.g., "March 2024")
33+
- **Expected Release Timeline**: Format must be in "Month YYYY"
3434
- **API Version**: The version of the API being released
3535
- **SDK Release Type**: Value must be beta or stable.
3636
- "beta" for preview API versions

.github/prompts/typespec-to-sdk.prompt.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,8 @@ Your goal is to guide user through the process of generating SDKs from TypeSpec
103103
1. Run `/create-release-plan`
104104
2. If SDK PRs exist, link them to the release plan
105105
3. Run `/sdk-details-in-release-plan` to add languages and package names to the release plan
106-
4. If TypeSpec project is for management plane, Run `/verify-namespace-approval` to check package namespace approval
106+
4. If TypeSpec project is for management plane, Run `/verify-namespace-approval` to check package namespace approval.
107+
This step should not check package readiness to verify namespace approval for management plane SDK.
107108
5. Run `/run-sdk-gen-pipeline` with the spec PR
108109
6. Monitor pipeline status and provide updates
109110
7. Display generated SDK PR links when available

0 commit comments

Comments
 (0)