-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: Remove default issue titles (#2999)
* Removes default issue titles as per today's discussion. * Removed Guidance issue template [skip ci]
- Loading branch information
Showing
4 changed files
with
39 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,34 +1,35 @@ | ||
--- | ||
name: Feature Request/Idea 🚀 | ||
about: Suggest a new feature or improvement (this does not mean you have to implement it) | ||
title: "Feature Request" | ||
labels: Issue-Feature | ||
assignees: '' | ||
|
||
--- | ||
|
||
<!-- | ||
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 | ||
I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: | ||
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. | ||
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. | ||
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). | ||
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. | ||
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. | ||
All good? Then proceed! | ||
--> | ||
|
||
# Description of the new feature/enhancement | ||
|
||
<!-- | ||
A clear and concise description of what the problem is that the new feature would solve. | ||
Describe why and how a user would use this new functionality (if applicable). | ||
--> | ||
|
||
# Proposed technical implementation details (optional) | ||
|
||
<!-- | ||
A clear and concise description of what you want to happen. | ||
--> | ||
--- | ||
name: "Feature Request/Idea 🚀" | ||
about: Suggest a new feature or improvement (this does not mean you have to implement | ||
it) | ||
title: '' | ||
labels: Issue-Feature | ||
assignees: '' | ||
|
||
--- | ||
|
||
<!-- | ||
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 | ||
I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: | ||
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. | ||
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. | ||
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). | ||
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. | ||
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. | ||
All good? Then proceed! | ||
--> | ||
|
||
# Description of the new feature/enhancement | ||
|
||
<!-- | ||
A clear and concise description of what the problem is that the new feature would solve. | ||
Describe why and how a user would use this new functionality (if applicable). | ||
--> | ||
|
||
# Proposed technical implementation details (optional) | ||
|
||
<!-- | ||
A clear and concise description of what you want to happen. | ||
--> |
This file was deleted.
Oops, something went wrong.