Skip to content
Prev Previous commit
Next Next commit
fix
  • Loading branch information
jeo02 authored and azure-sdk committed Aug 15, 2025
commit 465bf61019ca25dcfeafbd733661f315d57e7cee
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,11 @@ If any details are missing, prompt the user accordingly:
- Provide this resource: [Release Plan Creation Guide](https://eng.ms/docs/products/azure-developer-experience/plan/release-plan-create)
- Once all information is gathered, use `CreateReleasePlan` to create the release plan
- Display the newly created release plan details to the user for confirmation
- Refer [sdk details in release plan](sdk-details-in-release-plan.prompt.md) to identify languages configured in the TypeSpec project and add them to the release plan
- Refer [sdk details in release plan](sdk-details-in-release-plan.instructions.md) to identify languages configured in the TypeSpec project and add them to the release plan

## Step 5: Update SDK Details in Release Plan
- Run [sdk details in release plan](sdk-details-in-release-plan.prompt.md) to add languages and package names to the release plan
- If the TypeSpec project is for a management plane, run [verify namespace approval](verify-namespace-approval.prompt.md) if this is first release of SDK.
- Run [sdk details in release plan](sdk-details-in-release-plan.instructions.md) to add languages and package names to the release plan
- If the TypeSpec project is for a management plane, run [verify namespace approval](verify-namespace-approval.instructions.md) if this is first release of SDK.

## Step 6: Link SDK Pull Requests (if applicable)
- Ask the user if they have already created SDK pull requests locally for any programming language
Expand Down