Skip to content

Sync eng/common directory with azure-sdk-tools for PR 11931 #52630

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.

Sign up for GitHub

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
smw-ms merged 6 commits into from
Sep 15, 2025
Merged

Sync eng/common directory with azure-sdk-tools for PR 11931 #52630

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
05d6fdc
Update create release plan instructions and return
smw-ms Sep 2, 2025
db72d8e
Update eng/common/instructions/azsdk-tools/create-release-plan.instru…
smw-ms Sep 5, 2025
323a776
Return Release Plan Details
smw-ms Sep 5, 2025
2ef2ad2
Update eng/common/instructions/azsdk-tools/create-release-plan.instru…
smw-ms Sep 10, 2025
c2c159a
Add more specific rules for release plan creation
smw-ms Sep 10, 2025
793abd8
Add Better instructions
smw-ms Sep 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add more specific rules for release plan creation
  • Loading branch information
@smw-ms @azure-sdk
smw-ms authored and azure-sdk committed Sep 15, 2025
commit c2c159a89058beca1d8837391687beb211364013
4 changes: 1 addition & 3 deletions eng/common/instructions/azsdk-tools/create-release-plan.instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,7 @@ Your goal is to create a valid release plan. You must prompt user to provide all
> **Important Note**
> Do **not** ask the user to manually edit the DevOps work item.
> To update a release plan manually, the user must use the [Release Planner Tool](https://aka.ms/sdk-release-planner).
> When referring to a release plan in conversation with a user:
> - Always include both the **Release Plan Link** and **Release Plan ID** for clarity.
> - If the reference is intended for use by the LLM (e.g., for internal logic), use the **Release Plan Work Item ID** instead.
> When summarizing or displaying release plan details, do not mention or display the work item link/URL, or any direct reference to Azure DevOps work item resources. Only provide relevant release plan details like **Release Plan Link** and **Release Plan ID**.

Follow these steps in order to create or manage a release plan for an API specification pull request:

Expand Down