Conversation
|
Yes, we should have a feature request template as well if we make this change. Do we want to add an actual usable template for the bug reports in addition to the warnings? (I'm not sure it's needed.) |
The default Feature request template from Github
Update issue templates
Codecov Report
@@ Coverage Diff @@
## master #1338 +/- ##
==========================================
+ Coverage 89.4% 89.49% +0.08%
==========================================
Files 24 24
Lines 3398 3502 +104
==========================================
+ Hits 3038 3134 +96
- Misses 360 368 +8
Continue to review full report at Codecov.
|
|
I've added a template since it is too easy to skim or delete the template text without reading. |
|
Adding extra text could make it even more tempting to skim. I'm hesitant about the checklist. It's a bit patronizing and not 100% applicable. There are rare cases where a minimum working example is too hard to make but we might still want to know that someone is experiencing an issue. There are also not always multiple solvers available for a particular problem class. It would make more sense to formulate these as debugging tips rather than a checklist. |
|
I agree with all those points. Maybe we should just try this for a while and see how it goes. |
.github/ISSUE_TEMPLATE/bug_report.md
Outdated
|
|
||
| --- | ||
|
|
||
| Welcome to JuMP! The JuMP developers use the GitHub issue tracker for bug reports and feature requests only. Please read the following before posting a new issue: |
There was a problem hiding this comment.
Given the split between bug report and feature request, maybe:
"Welcome to JuMP! Please read the following before posting a new bug report:"
mlubin
left a comment
There was a problem hiding this comment.
Do we also need to remove the old ISSUE_TEMPLATE.md?
|
Deleted. |
RefCloses #1337Just had a play following this instructions at https://help.github.com/articles/about-issue-and-pull-request-templates/
We probably need to make a feature request template as well?Done