You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md
+3-13Lines changed: 3 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,29 +94,19 @@ Wait for the user to respond with a confirmation before proceeding to Step 1. Us
94
94
**Actions**:
95
95
1. Run `azsdk_get_sdk_pull_request_link` to fetch generated SDK PR info.
96
96
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
108
98
**Goal**: Create a release plan for the generated SDKs
109
99
**Actions**:
110
100
1. Refer to #file:create-release-plan.instructions.md to create a release plan using the spec pull request.
111
101
2. If the release plan already exists, display the existing plan details.
112
102
113
-
## Step 11: Mark Spec PR as Ready for Review
103
+
## Step 10: Mark Spec PR as Ready for Review
114
104
**Goal**: Update spec PR to ready for review status
115
105
**Actions**:
116
106
1. Prompt user to change spec PR to ready for review: "Please change the spec pull request to ready for review status"
117
107
2. Get approval and merge the spec PR
118
108
119
-
## Step 12: Release SDK Package
109
+
## Step 11: Release SDK Package
120
110
**Goal**: Release the SDK package using the release plan
121
111
**Actions**:
122
112
1. Run `ReleaseSdkPackage` to release the SDK package.
0 commit comments