Skip to content

Commit 0f22c1a

Browse files
Remove CODEOWNERS and service labels instructions until it can be inserted into a more contextually appropriate location for the user (#43098)
Co-authored-by: Daniel Jurek <[email protected]>
1 parent 940c7a4 commit 0f22c1a

File tree

1 file changed

+3
-13
lines changed

1 file changed

+3
-13
lines changed

eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -94,29 +94,19 @@ Wait for the user to respond with a confirmation before proceeding to Step 1. Us
9494
**Actions**:
9595
1. Run `azsdk_get_sdk_pull_request_link` to fetch generated SDK PR info.
9696

97-
## Step 9: Validate Label and Codeowners
98-
**Goal**: Validate the label and all codeowners for a service. Create new label and codeowner entry if none exist.
99-
**Actions**:
100-
1. To validate a service label refer to #file:./validate-service-label.instructions.md
101-
2. After service label is validated or created refer to #file:./validate-codeowners.instructions.md
102-
3. Handle post-validation actions based on results:
103-
- **If both label and codeowners were already valid**: Prompt user "Your service label and codeowners are already properly configured. Would you like to modify the existing codeowners entry for your service?"
104-
- **If new label or codeowner entries were created**: Display details of the label and codeowners PR if they were created, then prompt user "The following PRs have been created for your service configuration: [list PRs]. Would you like to make any additional modifications to these entries?"
105-
**Success Criteria**: Service label exists and codeowners are properly configured with at least 2 valid owners. For created entries, showcase all PR's.
106-
107-
## Step 10: Create release plan
97+
## Step 9: Create release plan
10898
**Goal**: Create a release plan for the generated SDKs
10999
**Actions**:
110100
1. Refer to #file:create-release-plan.instructions.md to create a release plan using the spec pull request.
111101
2. If the release plan already exists, display the existing plan details.
112102

113-
## Step 11: Mark Spec PR as Ready for Review
103+
## Step 10: Mark Spec PR as Ready for Review
114104
**Goal**: Update spec PR to ready for review status
115105
**Actions**:
116106
1. Prompt user to change spec PR to ready for review: "Please change the spec pull request to ready for review status"
117107
2. Get approval and merge the spec PR
118108

119-
## Step 12: Release SDK Package
109+
## Step 11: Release SDK Package
120110
**Goal**: Release the SDK package using the release plan
121111
**Actions**:
122112
1. Run `ReleaseSdkPackage` to release the SDK package.

0 commit comments

Comments
 (0)