-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Adding new issue template #1206
Adding new issue template #1206
Conversation
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.
The feature request template is not really applicable; algorithms are not to be requested (rather, PRs should be opened directly). The bug template should probably have a "bug" label. Hints to the one opening the issue such as "Before you open an issue ..." should be comments.
I still think we should keep the feature request template. For example: what if I want to add a new workflow or functionality and make an issue before making any PRs? |
We should explicitly mention in the issue template that it is not for requesting algorithms imo. |
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.
Wrong indentation.
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.
Looks great. Thanks! 🚀
@Panquesito7 @appgurueu Since there is not much time until the end of the Hactoberfest, would you mind adding the |
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.
Great, thanks! 🚀
know more
Solves issue #1204
Describe your change:
Checklist:
Example:
UserProfile.js
is allowed butuserprofile.js
,Userprofile.js
,user-Profile.js
,userProfile.js
are notFixes: #{$ISSUE_NO}
.