Skip to content

chore(github): update enhancement request issue template #3900

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

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

chore(github): update enhancement request issue template #3900

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/enhancement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
name: Enhancement Request
about: Suggest an enhancement to the gateway-api project
labels: kind/feature
labels: kind/gep
Copy link
Member

Choose a reason for hiding this comment

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

🤔 It seems like we won't want every feature request to necessarily be a GEP. IMO, issues should probably only transition to kind/gep once we have a GEP PR open (or about to be), and kind/feature can continue to be used to represent feature requests that are earlier along in their lifecycle. Not intended to be a blocking comment here, just want to see how you or others view the ideal distinction between these.


---
<!-- Please only use this template for submitting enhancement requests -->
Expand Down