-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add bug report and feature request GitHub Issues template #114
Conversation
For a bug report, please copy and paste any error messages from the application or command-line here. | ||
For a feature request, Please state how the new functionality could potentially benefit the community. | ||
--> | ||
|
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.
Inspired by the way conda-forge instructs users. <!--, -->
remains invisible when rendered, so the user does not have to delete this.
@@ -6,7 +6,7 @@ labels: "release" | |||
assignees: "" | |||
--- | |||
|
|||
**Release checklist for GitHub contributors** | |||
### Release checklist for GitHub contributors |
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.
Was recommended by my IDE linter to use ###
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.
Ready for review - combined both feature/bug report into a single issue as discussed.
I kept it simple because I realized that I don't really like populating many textboxes when creating issues.
Once merged, I will also update my forked cookiecutter repo and test locally, then make a PR there.
@sbillinge ready for review |
No description provided.