Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch issue templates to use new-style issue types #13289

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Switch issue templates to use new-style issue types #13289

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/BUG_REPORT.yaml → .github/ISSUE_TEMPLATE/01-bug.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: 🐛 Bug report
description: Create a report to help us improve 🤔.
labels: ["bug"]
type: Bug

body:
- type: markdown
Expand Down
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/FEATURE_REQUEST.yaml → .github/ISSUE_TEMPLATE/02-feature.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: 🚀 Feature request
description: Suggest an idea for this project 💡!
labels: ["type: feature request"]
type: Enhancement
Copy link
Contributor

Choose a reason for hiding this comment

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

We currently have in the label space type: enhancement and type: feature request, each with different meaning, namely "improve existing functionality" and "suggest or ask new feature", respectively. Assuming we want to have those 2 concepts captured in issue types (I would vote for it) It would be good to preserve this separation by naming the type here with Feature or something similar, but not Enhancement.

Copy link
Member Author

Choose a reason for hiding this comment

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

We have to set the allowed types at the organisation level (if I understand the docs correctly), but that seems easily doable.


body:
- type: markdown
Expand Down