Add Copilot instructions for PR labeling #5531

Activity

1. Andy Jordan (andyleejordan)

   assigned

   Copilot

   and

   Andy Jordan (andyleejordan)

   on Jun 18, 2026
2. github-actions

   added

   Area-Build Release

   Issue-EnhancementA feature request (enhancement).A feature request (enhancement).

   Needs: TriageMaintainer attention needed!Maintainer attention needed!

   on Jun 18, 2026
3. github-actions commented on Jun 18, 2026

   

   github-actionsBot

   on Jun 18, 2026 – with GitHub Actions

   Contributor

   More actions

   Triage summary: Add PR labeling guidance to .github/copilot-instructions.md so Copilot agents (and contributors) know to apply Issue-Bug / Issue-Enhancement labels, which drive changelog categorization in .github/release.yml.

   For maintainers

   Reproducibility: Not a bug — this is a missing-guidance enhancement. The need is unambiguous: .github/copilot-instructions.md exists and covers build/architecture but has no mention of PR labeling. .github/release.yml already categorizes merged PRs by Issue-Enhancement and Issue-Bug labels. Without instructions, Copilot agents open unlabeled PRs that land in "Other Changes 🙏" regardless of their nature. Confidence in scope: high.

   Copilot-fix suitability: Yes. This is an ideal candidate:

   • Single-file change (append a short section to .github/copilot-instructions.md)
   • Clear expected behavior: PRs opened by Copilot agents should carry the correct Issue-* label
   • Reference implementation available: PowerShellEditorServices#2310
   • No design decisions or protocol work needed
   • Already assigned to the Copilot coding agent

   Likely area: .github/copilot-instructions.md — add a "PR labeling" section explaining that every PR must carry exactly one Issue-Enhancement or Issue-Bug label (matching .github/release.yml) so automated release notes categorize it correctly.

   Suggested section content (adapt from PSES PR):

   ## Pull Request Labels
   
   Every pull request **must** carry exactly one `Issue-*` label. GitHub's automated
   release notes (`.github/release.yml`) use these labels to categorize merged PRs:
   
   | Label               | Changelog section              |
   |---------------------|-------------------------------|
   | `Issue-Enhancement` | Enhancements & Features ✨    |
   | `Issue-Bug`         | Squashed Bugs 🐛              |
   | *(anything else)*   | Other Changes 🙏              |
   
   Apply the label that best describes the change before requesting review.

   Generated by Agentic Issue Triage for issue #5531 · 74.6 AIC · ⌖ 12.5 AIC · ⊞ 23.4K · ◷

   Add this agentic workflows to your repo

   To install this agentic workflow, run

   gh aw add githubnext/agentics/workflows/issue-triage.md@2f03fdaafb8c1ae62dfde7e0be762a822a201aeb
   
4. Andy Jordan (andyleejordan)

   closed this as completedon Jun 18, 2026