github/azure-sdk-for-cpp
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
5f482ad149
azure-sdk-for-cpp/eng/common/instructions/azsdk-tools/check-package-readiness.instructions.md
Azure SDK Bot 5f482ad149
Sync eng/common directory with azure-sdk-tools for PR 11477 (#6700) 
* 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>
2025-08-18 09:46:15 -07:00

1.4 KiB
Raw Blame History

description
This prompt is designed to check the release readiness of a SDK package.

Goal

Check the release readiness of an SDK package by collecting the required information from the user and executing the readiness check.

Instructions

  1. Collect Required Information:

    • Prompt the user for the exact package name
    • Prompt the user to select the programming language from the following options (case sensitive):
      • Python
      • Java
      • JavaScript
      • .NET
      • Go

  2. Execute Readiness Check:

    • Use the CheckPackageReleaseReadiness tool with the provided package name and selected language
    • Do not check for existing pull requests to run this step.
    • Do not ask the user to create a release plan to run this step.

  3. Present Results:

    • If the package is ready for release, highlight and provide the link to the release pipeline
    • If the package is not ready, display the specific issues that need to be resolved

  4. Follow-up Actions:

    • Provide clear next steps based on the readiness status
    • If issues are found, offer guidance on how to resolve them

Expected User Interaction Flow

  1. Ask: "What is the exact name of the package you want to check for release readiness?"
  2. Ask: "Please select the programming language for this package: Python, Java, JavaScript, .NET, or Go"
  3. Execute the readiness check using the provided information
  4. Display results and next steps