From 61a7bf51a8f9acff43d9c1cf24783e34f8e36100 Mon Sep 17 00:00:00 2001 From: azure-sdk Date: Wed, 6 May 2026 23:13:35 +0000 Subject: [PATCH] Sync eng/common directory with azure-sdk-tools repository --- .../instructions/azsdk-tools/typespec-to-sdk.instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md b/eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md index 4d0e4bb2e39e..dc5f54221240 100644 --- a/eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md +++ b/eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md @@ -71,7 +71,7 @@ Follow the steps in #file:.github/skills/azsdk-common-generate-sdk-locally/SKILL 3. Prompt the user to provide the API spec pull request link if not already available in the current context. 4. If unsure, check if a release plan already exists for API spec pull request. 5. Prompt user to find the service id and product id in service tree `aka.ms/st` and provide them. Stress the importance of correct service id and product id for proper release plan creation. -6. If a new release plan is needed, refer to #file:.github/skills/azsdk-common-prepare-release-plan/SKILL.md to create a release plan using the spec pull request. API spec pull request is required to create a release plan. +6. If a new release plan is needed, refer to #file:.github/skills/azsdk-common-prepare-release-plan/SKILL.md to create a release plan using the spec pull request or TypeSpec project path. 7. Prompt user to change spec PR to ready for review: "Please change the spec pull request to ready for review status" 8. Suggest users to follow the instructions on spec PR to get approval from API reviewers and merge the spec PR. 9. Link SDK pull requests to the release plan.