Skip to content

Remove servicing PR template from Copilot instructions#37761

Merged
AndriySvyryd merged 2 commits into
mainfrom
copilot/remove-servicing-template
Feb 21, 2026
Merged

Remove servicing PR template from Copilot instructions#37761
AndriySvyryd merged 2 commits into
mainfrom
copilot/remove-servicing-template

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Feb 21, 2026

The servicing PR description template (with Description, Customer impact, How found, Regression, Testing, Risk sections) has been removed from .github/copilot-instructions.md. The PR Guidelines section now only retains the instruction to target main for new PRs.

Original prompt

Remove the servicing template from copilot instructions


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Copilot AI changed the title [WIP] Remove servicing template from copilot instructions Remove servicing PR template from Copilot instructions Feb 21, 2026
Copilot AI requested a review from AndriySvyryd February 21, 2026 02:01
@AndriySvyryd AndriySvyryd reopened this Feb 21, 2026
@AndriySvyryd AndriySvyryd marked this pull request as ready for review February 21, 2026 08:05
@AndriySvyryd AndriySvyryd requested a review from a team as a code owner February 21, 2026 08:05
Copilot AI review requested due to automatic review settings February 21, 2026 08:05
Copy link
Copy Markdown

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 pull request removes the servicing PR description template from the Copilot instructions file. The template previously provided a structured format for PRs targeting release branches, including sections for Description, Customer impact, How found, Regression, Testing, and Risk. The removal simplifies the PR Guidelines section to focus solely on the instruction to target the main branch for new PRs.

Changes:

  • Removed the servicing PR template from .github/copilot-instructions.md
  • Simplified the Pull Request Guidelines section

Copy link
Copy Markdown
Member

@roji roji left a comment

Choose a reason for hiding this comment

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

@AndriySvyryd do we want to find an alternative before removing this?

Unfortunately there doesn't seem to be a way to conditionally include instructions ("lazy load") into copilot-instructions.md (e.g. based on the target branch). We could maybe try hacking this via a skill (which itself is lazy loaded) but that's getting convoluted and possibly brittle.

We can go with the approach you proposed of having a traditional workflow to post the comment with the template, if you want...

@AndriySvyryd AndriySvyryd merged commit fb11d70 into main Feb 21, 2026
16 checks passed
@AndriySvyryd AndriySvyryd deleted the copilot/remove-servicing-template branch February 21, 2026 20:35
@AndriySvyryd
Copy link
Copy Markdown
Member

@AndriySvyryd do we want to find an alternative before removing this?

Unfortunately there doesn't seem to be a way to conditionally include instructions ("lazy load") into copilot-instructions.md (e.g. based on the target branch). We could maybe try hacking this via a skill (which itself is lazy loaded) but that's getting convoluted and possibly brittle.

We can go with the approach you proposed of having a traditional workflow to post the comment with the template, if you want...

I'll try adding a skill. I'm afraid that CCA would ignore comments posted by a bot

@roji
Copy link
Copy Markdown
Member

roji commented Feb 21, 2026

Yeah, in any case I agree that a skill here is better than having the template in the instructions...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants