Skip to content

Commit 12b1ba4

Browse files
jeo02azure-sdk
authored andcommitted
remove uneeded headers
1 parent 2aad8e2 commit 12b1ba4

10 files changed

+0
-26
lines changed

eng/common/instructions/azsdk-tools/check-api-readiness.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
---
2-
mode: 'agent'
3-
tools: ['CheckApiReadyForSDKGeneration', 'codebase', 'GetPullRequest', 'GetGitHubUserDetails', 'GetPullRequestForCurrentBranch']
42
description: 'Check API Readiness for SDK Generation'
53
---
64
Your goal is to check if API spec pull request is ready for SDK generation. Identify the next action required from user based on the comments on spec pull request if spec is not ready and notify the user.

eng/common/instructions/azsdk-tools/check-package-readiness.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
---
2-
mode: 'agent'
3-
tools: ['CheckPackageReleaseReadiness']
42
description: 'This prompt is designed to check the release readiness of a SDK package.'
53
---
64
## Goal

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

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,3 @@
1-
---
2-
mode: 'agent'
3-
tools: ['CreateReleasePlan', 'GetReleasePlanForPullRequest', 'GetReleasePlan', 'LinkSdkPullRequestToReleasePlan']
4-
---
5-
61
# Release Plan Creation Process
72
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.
83
Follow these steps in order to create or manage a release plan for an API specification pull request:

eng/common/instructions/azsdk-tools/create-sdk-locally.instructions.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
mode: 'agent'
3-
tools: ['codebase']
4-
---
51
Your goal is to help guide the user to create SDK locally for TypeSpec changes. This is currently supported for **Python** only. User can generate SDK for other languages using SDK generation pipeline.
62
## Steps to create Python SDK locally from TypeSpec
73
### Step 1: Check for existing azure-sdk-for-python repository
Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
mode: 'agent'
3-
tools: ['codebase', 'CreatePullRequest', 'GetModifiedTypeSpecProjects', 'GetGitHubUserDetails', 'CheckIfSpecInPublicRepo', 'GetPullRequest', 'GetPullRequestForCurrentBranch']
4-
---
51
Your goal is to identify modified TypeSpec project in current branch and create a pull request for it.
62
Check if a pull request already exists using GetPullRequestForCurrentBranch. If a pull request exists, inform the user and show the pull request details. If no pull request exists, create a new pull request using CreatePullRequest.
73

eng/common/instructions/azsdk-tools/run-sdk-gen-pipeline.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
---
2-
mode: 'agent'
3-
tools: ['GenerateSDK', 'GetSDKPullRequestDetails', 'GetReleasePlan', 'GetReleasePlanForPullRequest', 'GetPipelineRun', 'GetPipelineRunStatus', 'LinkSdkPullRequestToReleasePlan']
42
description: 'Generate SDKs from TypeSpec using pipeline'
53
---
64
Your goal is to generate SDKs from the TypeSpec spec pull request. Get API spec pull request link for current branch or from user if not available in current context.

eng/common/instructions/azsdk-tools/sdk-details-in-release-plan.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
---
2-
mode: 'agent'
32
description: 'Identify languages configured in the TypeSpec project and add it to release plan'
4-
tools: ['GetReleasePlanForPullRequest', 'GetReleasePlan', 'UpdateReleasePlanSDKInfo']
53
---
64
# Step 1: Find the list of languages and package names
75
**Goal**: Identify languages configured in the TypeSpec project and generate the json object with language and package name.

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
mode: 'agent'
32
description: 'Generate SDKs from TypeSpec'
43
---
54
Your goal is to guide user through the process of generating SDKs from TypeSpec projects. Show all the high level steps to the user to ensure they understand the flow. Use the provided tools to perform actions and gather information as needed.

eng/common/instructions/azsdk-tools/validate-typespec.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
11
---
2-
mode: 'agent'
3-
tools: ['RunTypeSpecValidation']
42
description: 'Validate TypeSpec'
53
---
64
Your goal is identify the TypeSpec project root if not available in current context and validate TypeSpec project.

eng/common/instructions/azsdk-tools/verify-namespace-approval.instructions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
---
2-
mode: 'agent'
32
description: 'Verify SDK namespace approval for management plane'
4-
tools: ['GetReleasePlan', 'GetReleasePlanForPullRequest', 'LinkNameSpaceApprovalIssue']
53
---
64
This task is required only for management plane API spec and only if a release plan exists for the API spec pull request.
75

0 commit comments

Comments
 (0)