Skip to content

Conversation

@azure-sdk
Copy link
Collaborator

Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#12516 See eng/common workflow

@azure-sdk azure-sdk requested a review from a team as a code owner October 30, 2025 21:05
@azure-sdk azure-sdk requested review from Copilot and smw-ms October 30, 2025 21:05
@azure-sdk azure-sdk added EngSys This issue is impacting the engineering system. Central-EngSys This issue is owned by the Engineering System team. labels Oct 30, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR restructures the release plan creation instructions for LLMs by consolidating critical instructions, removing redundant checks, and renumbering the process steps.

Key Changes:

  • Enhanced LLM instructions with clearer formatting and an additional directive about following NextSteps field responses
  • Removed "Check Existing Release Plan" step to streamline the workflow
  • Renumbered all steps (Step 2-7 became Step 2-6) and added guidance for handling existing release plans within the creation step

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

> Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
> All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
> Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
> **CRITICAL INSTRUCTIONS FOR LLM***
Copy link

Copilot AI Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove extra asterisk from 'LLM***' - should be 'LLM**' to properly close the markdown bold formatting.

Suggested change
> **CRITICAL INSTRUCTIONS FOR LLM***
> **CRITICAL INSTRUCTIONS FOR LLM**

Copilot uses AI. Check for mistakes.
Comment on lines +32 to 33
- If existing release plans are found, extract and display key information: Release Plan ID, status, associated languages, SDK PRs
- Display the newly created release plan details to the user for confirmation
Copy link

Copilot AI Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line appears to contradict the removal of Step 2 'Check Existing Release Plan'. The instruction to handle existing release plans is now embedded in Step 3, but there's no clear indication of when or how 'existing release plans are found' since the explicit check step was removed. Consider clarifying whether this refers to the response from azsdk_create_release_plan if a plan already exists, or if there's an implicit check within that tool call.

Suggested change
- If existing release plans are found, extract and display key information: Release Plan ID, status, associated languages, SDK PRs
- Display the newly created release plan details to the user for confirmation
- If the response from `azsdk_create_release_plan` indicates that existing release plans are present, extract and display key information: Release Plan ID, status, associated languages, SDK PRs
- If a new release plan is created, display its details to the user for confirmation

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Central-EngSys This issue is owned by the Engineering System team. EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants