github/azure-sdk-for-cpp
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Sync eng/common directory with azure-sdk-tools for PR 11931 (#6739)

Browse Source 
* Update create release plan instructions and return

* Update eng/common/instructions/azsdk-tools/create-release-plan.instructions.md

Co-authored-by: Mariana Rios Flores <mariari@microsoft.com>

* Return Release Plan Details

* Update eng/common/instructions/azsdk-tools/create-release-plan.instructions.md

Co-authored-by: Ben Broderick Phillips <ben@benbp.net>

* Add more specific rules for release plan creation

* Add Better instructions

---------

Co-authored-by: Summer Warren <summerwarren@microsoft.com>
Co-authored-by: Mariana Rios Flores <mariari@microsoft.com>
Co-authored-by: Ben Broderick Phillips <ben@benbp.net>
This commit is contained in:
Azure SDK Bot 2025-09-15 11:29:45 -07:00 committed by GitHub
parent 0d8b1bbf6b
commit ad03f7be56
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
eng/common/instructions/azsdk-tools/create-release-plan.instructions.md
View File

@ -1,5 +1,10 @@
> **Important Note for LLM**
> Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
> All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
> Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
# Release Plan Creation Process
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.
Your 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.
Follow these steps in order to create or manage a release plan for an API specification pull request:
## Step 1: Validate Prerequisites