Skip to content

Create bugs as bug issues rather than tagging them as bugs#15617

Merged
davidfowl merged 1 commit intomicrosoft:mainfrom
afscrome:patch-17
Mar 26, 2026
Merged

Create bugs as bug issues rather than tagging them as bugs#15617
davidfowl merged 1 commit intomicrosoft:mainfrom
afscrome:patch-17

Conversation

@afscrome
Copy link
Contributor

@afscrome afscrome commented Mar 26, 2026

Description

Based on #15578 (comment), change the bug issue template to use the bug issue type rather than tagging the issue as bug.

Additionally you may want to consider assigning these issues to a project to help with any triaging processes you do.

projects: ["octo-org/1", "octo-org/44"]

Copilot AI review requested due to automatic review settings March 26, 2026 08:41
@github-actions
Copy link
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15617

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 15617"

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

Updates the bug report issue template to use an Issue Type (“Bug”) instead of applying the bug label, aligning with the desired “create bugs as bug issues” workflow.

Changes:

  • Removed automatic application of the bug label from the bug report issue form.
  • Added a top-level type: Bug field to attempt to create issues with the Bug issue type.

name: 🐞 Bug Report
description: Create a report about something that is not working
labels: ["bug"]
type: Bug
Copy link

Copilot AI Mar 26, 2026

Choose a reason for hiding this comment

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

GitHub Issue Forms (issue template YAML) schema has historically only supported top-level keys like name, description, title, labels, assignees, and body. A top-level type: Bug is likely not recognized and may be ignored (or cause template validation issues), meaning new issues won’t actually be created with the Bug issue type. If the repo wants Bug Issue Type assignment, consider keeping labels: [\"bug\"] and using automation (e.g., a GitHub Action on issues.opened to map label -> issue type), or confirm the exact supported template key/value for setting an issue type per current GitHub docs and update accordingly.

Suggested change
type: Bug

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Syntax taken from https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

name: Bug Report
description: File a bug report.
title: "[Bug]: "
labels: ["bug", "triage"]
projects: ["octo-org/1", "octo-org/44"]
assignees:
  - octocat
type: bug
body:

@davidfowl davidfowl enabled auto-merge (squash) March 26, 2026 13:45
@davidfowl davidfowl merged commit a27bc9c into microsoft:main Mar 26, 2026
257 of 258 checks passed
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.

3 participants