Skip to content

Sync eng/common directory with azure-sdk-tools repository#7107

Open
azure-sdk wants to merge 1 commit intoAzure:mainfrom
azure-sdk:sync-eng/common
Open

Sync eng/common directory with azure-sdk-tools repository#7107
azure-sdk wants to merge 1 commit intoAzure:mainfrom
azure-sdk:sync-eng/common

Conversation

@azure-sdk
Copy link
Copy Markdown
Collaborator

Sync eng/common directory with azure-sdk-tools repository

Copilot AI review requested due to automatic review settings May 6, 2026 23:13
@azure-sdk azure-sdk requested a review from a team as a code owner May 6, 2026 23:13
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR syncs content under eng/common with the upstream azure-sdk-tools repository, updating the TypeSpec-to-SDK workflow instructions used by automation and contributors.

Changes:

  • Updates the SDK release plan step to reference creating a release plan from either a spec PR or a TypeSpec project path.
  • Fixes formatting/line alignment in the release plan step list.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants