Skip to content

Commit 9ca6ee0

Browse files
committed
added templates
1 parent 50fddcc commit 9ca6ee0

File tree

2 files changed

+52
-0
lines changed

2 files changed

+52
-0
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: Bug report
3+
about: Help us track down bugs in SCIP
4+
5+
---
6+
7+
Welcome to SCIP and thank you for reporting a bug!
8+
9+
Please read the following before posting a new bug report:
10+
11+
- If you have a question or are unsure if the behavior you're experiencing is expected, also feel free to reach out on the [mailing list](http://listserv.zib.de/mailman/listinfo/scip/).
12+
13+
- If you are reasonably confident your issue is a bug in SCIP, this is the right place. Be sure to include as much relevant information as possible, including a minimal reproducible example. See https://help.github.com/articles/basic-writing-and-formatting-syntax/ for background on how to format text and code on GitHub issues.
14+
15+
- If the issue occurs when running an instance, be sure to include it, along with any non-default setting.
16+
If the issue occurs with a model built programmatically, include a minimal script producing the model.
17+
You can use `SCIPwriteOrigProblem(scip, "my_model.lp", NULL, FALSE)` to write the model to a file.
18+
19+
- If the problem is SCIP producing an incorrect solution, be sure to include a reference solution as a sol file, produced either by SCIP or another solver.
20+
You can also use `SCIPprintSol(scip, SCIPgetBestSol(scip), file, FALSE)` to print a solution to a file.
21+
22+
Thanks for contributing to SCIP!
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
### Description
2+
3+
[Add a description of the introduced changes here.]
4+
5+
### Code review
6+
7+
* [ ] The code change is correct.
8+
* [ ] The naming and place of new methods is clear and consistent **or** no new methods have been added.
9+
* [ ] Emphasis settings are up to date.
10+
* [ ] Ensure that new code and features use randomization where necessary to account for performance variability.
11+
* [ ] The code is sufficiently documented.
12+
* [ ] The coding style is OK, see https://scipopt.org/doc/html/CODE.php.
13+
14+
### Documentation and building
15+
16+
* [ ] The CHANGELOG is up to date (including API changes if present in this MR).
17+
* [ ] The user documentation is up to date (doc/xternal.c, doc/inc/faq/, installation instructions, ...).
18+
* [ ] Both build systems and makedist.sh are up to date. Especially, newly added, renamed or removed source files have been added to, renamed in or removed from src/CMakeLists.txt.
19+
20+
### Testing
21+
22+
* [ ] ctest passes without errors.
23+
* [ ] The performance impact has been checked **or** the changed code will not be executed by default.
24+
* [ ] The new code is sufficiently covered by tests (perhaps, new coverage settings or new unit tests have been added).
25+
26+
### Does this merge request introduce an API change? :warning:
27+
28+
* [ ] No, **or** as far as possible, the code ensures backwards compatibility.
29+
* [ ] No, **or** the `SCIP_APIVERSION` is updated (use label 'public SCIP API'; in particular if new `SCIP_EXPORT` methods have been added).
30+
* [ ] No parameter was added/deleted/changed **or** the MR is tagged with the label 'default parameter'. (This includes the addition of parameters by adding/deleting a plugin.)

0 commit comments

Comments
 (0)