5f482ad149
* place prompts in common place * Update eng/common/instructions/azsdk-tools/create-sdk-locally.prompt.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/common/instructions/azsdk-tools/verify-namespace-approval.prompt.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/common/instructions/azsdk-tools/typespec-to-sdk.prompt.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update eng/common/instructions/azsdk-tools/typespec-to-sdk.prompt.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * rename to .instructions.md * remove uneeded headers * change to .instructions * fix * run to refer to * relative links fix --------- Co-authored-by: Juan Ospina <70209456+jeo02@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
443 B
443 B
| description |
|---|
| Check API Readiness for SDK Generation |
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. Before running, get spec pull request link for current branch or from user if not available in current context. If pull request has APIView links, then highlight them to user.