-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
New Issue Templates #1056
New Issue Templates #1056
Conversation
As per earlier discussion @MikhailZex, I have drafted a feature request template, to deprecate using #867. |
@MikhailZex requesting urgent review. The new config prevents users from opening an issue without using a template. |
Yeah github only takes the config file from the master branch. Once the PR is merged then you won't be able to make template-less issues |
Ok. Are you trying to enforce templates or allow template-less issues? |
Enforce templates. Prevent issues like #1050 from happening etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor changes to be made.
|
||
## Solution | ||
<!--- How can we fix this problem? Describe the feature you are requesting. --> | ||
<!--- Address Pros & Cons of the feature. If you present multiple solutions, please state them separately, and compare at the end --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a little overkill. Something along the lines of "describe a possible implementation you have in mind (if you do have any ideas as of now)"
|
||
## Examples/Research | ||
<!--- Have you tried to solve your problem? --> | ||
<!--- Can you provide code examples, diagrams or any other information to support the Feature Request? --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most people wouldn't do this. Drop it.
## Purpose | ||
<!--- Describe the problem or feature in addition to a link to the issues. --> | ||
|
||
## Approach |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Design
would be more apt.
<!--- Describe the problem or feature in addition to a link to the issues. --> | ||
|
||
## Approach | ||
<!--- How does this change address the problem? --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Force simplicity "Describe then solution implemented in around 50 words. Please be specific."
The current phrasing is open to vague replies.
<!--- Change the title to summarise simply and succintly. --> | ||
|
||
## Problem | ||
<!--- IMPORTANT: Why do we need to implement this feature? How would it help you? --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*how would this help other users?
Features that help only few users won't be implemented. They can fork spotDL, make changes and will link those in the readme.
No description provided.