Skip to content

Update backport prompt#26392

Merged
TravisEz13 merged 8 commits into
PowerShell:masterfrom
TravisEz13:backport-prompt-update
Nov 5, 2025
Merged

Update backport prompt#26392
TravisEz13 merged 8 commits into
PowerShell:masterfrom
TravisEz13:backport-prompt-update

Conversation

@TravisEz13

Copy link
Copy Markdown
Member

This pull request updates the backport PR process documentation to clarify labeling requirements and branch naming conventions, and adds important steps for changelog management and tracking the backport status. These changes help ensure backport PRs are properly categorized, tracked, and easier to maintain.

Labeling and changelog management:

  • Added instructions to apply the original PR's changelog label (CL-*) to the backport PR, ensuring proper categorization in release changelogs.
  • Added steps to update labels on the original PR after backporting (add Migrated, remove Consider/Approved) to clearly track backport status. [1] [2]
  • Updated the checklist to require CL label addition and original PR label updates for backports.

Branch naming convention:

  • Changed manual backport branch naming format to backport/release/<version>/pr/<pr-number> for improved clarity and consistency with automated backports.

CI/CD context:

  • Added guidance for CI/CD infrastructure changes, noting the importance of backporting such changes to avoid future technical debt, even if risk is higher.

Copilot AI review requested due to automatic review settings November 5, 2025 19:19
@TravisEz13 TravisEz13 added the CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log label Nov 5, 2025

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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 updates the backport process documentation to include additional steps for labeling and tracking backported PRs. The changes enhance the workflow by adding changelog label management and updating the branch naming convention.

  • Adds steps for applying changelog labels to backport PRs and updating original PR labels
  • Includes guidance on CI/CD change considerations in risk assessment
  • Updates branch naming convention to use a more structured format

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

Comment thread .github/prompts/backport-pr-to-release-branch.prompt.md Outdated
Comment thread .github/prompts/backport-pr-to-release-branch.prompt.md Outdated
TravisEz13 and others added 2 commits November 5, 2025 11:21
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@TravisEz13 TravisEz13 enabled auto-merge (squash) November 5, 2025 19:22
@TravisEz13 TravisEz13 merged commit ac55117 into PowerShell:master Nov 5, 2025
36 checks passed
@TravisEz13 TravisEz13 deleted the backport-prompt-update branch November 5, 2025 19:23
SIRMARGIN pushed a commit to SIRMARGIN/PowerShell that referenced this pull request Dec 12, 2025
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
kilasuit pushed a commit to kilasuit/PowerShell that referenced this pull request Jan 2, 2026
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
JustinGrote pushed a commit to JustinGrote/PowerShell that referenced this pull request Jun 2, 2026
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-Docs Indicates that a PR should be marked as a documentation change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants