Skip to content

chore: add feature request issue template #913

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

Merged
merged 3 commits into from
Apr 7, 2022
Merged

chore: add feature request issue template #913

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d0f01ad
chore: add feature request issue template
jsjoeio Apr 7, 2022
7a68d16
Update .github/ISSUE_TEMPLATE/feature.md
jsjoeio Apr 7, 2022
bac6795
Update .github/ISSUE_TEMPLATE/feature.md
jsjoeio Apr 7, 2022
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
Next Next commit
chore: add feature request issue template
  • Loading branch information
@jsjoeio
jsjoeio committed Apr 7, 2022
commit d0f01adc3b7e4decbedeefec727fdc1233c67ca8
14 changes: 14 additions & 0 deletions .github/ISSUE_TEMPLATE/feature.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
name: Feature request
about: Suggest an idea to improve coder
title: "Enhancement: "
Copy link
Member

Choose a reason for hiding this comment

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

I see we have a type: enhancement label as well, should we name this Feature to make room for an enhancement template?

Also do we need the prefixes or are the labels enough?

Copy link
Contributor

Choose a reason for hiding this comment

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

Let's just consolidate the type: enhancement applications to this feature one, having both seems unnecessary

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes! @vapurrmaid said the same thing. Updated!

Also do we need the prefixes or are the labels enough?

Probably not but the others have it and I think we should be consistent. So if we change here, we should change on the other templates. Thoughts?

Copy link
Member

@code-asher code-asher Apr 7, 2022 •
edited
Loading

Choose a reason for hiding this comment

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

Let's just consolidate

Makes sense to me! I am definitely in favor of that as it is always a headache opening a ticket trying to decide between them.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay I think I understood you both right! Let me know if I missed something

Copy link
Member

Choose a reason for hiding this comment

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

Ohhh I mean the prefixes in the issues like [Bug]: Fix this bug and then also tagging with bug.

I actually quite like the prefixes in the labels personally!

Copy link
Contributor

Choose a reason for hiding this comment

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

I do too, but I defer to @misskniss here.

Copy link
Member

@code-asher code-asher Apr 7, 2022 •
edited
Loading

Choose a reason for hiding this comment

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

Completely fair. Are we good with making Bug:, Feat:, and Docs: prefixes in issue titles our pattern? @misskniss Or would we rather without?

Copy link
Member

Choose a reason for hiding this comment

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

(I say go ahead and merge though if we do end up removing them we can do it separately.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

(I say go ahead and merge though if we do end up removing them we can do it separately.)

Sounds good!

labels: "new feature"
---

## What is your suggestion?

## Why do you want this feature?

## Are there any workarounds to get this functionality today?

## Are you interested in submitting a PR for this?