Fix 'check' in markdown for github templates
This commit is contained in:
parent
4636bf6160
commit
b46c7dddaa
|
@ -2,7 +2,7 @@ Thanks for submitting an issue!
|
|||
|
||||
Here's a quick checklist in what to include:
|
||||
|
||||
[ ] Include a detailed description of the bug or suggestion
|
||||
[ ] `pip list` of the virtual environment you are using
|
||||
[ ] py.test and operating system versions
|
||||
[ ] Minimal example if possible
|
||||
- [ ] Include a detailed description of the bug or suggestion
|
||||
- [ ] `pip list` of the virtual environment you are using
|
||||
- [ ] py.test and operating system versions
|
||||
- [ ] Minimal example if possible
|
||||
|
|
|
@ -2,7 +2,7 @@ Thanks for submitting a PR, your contribution is really appreciated!
|
|||
|
||||
Here's a quick checklist that should be present in PRs:
|
||||
|
||||
[ ] Target: for bug or doc fixes, target `master`; for new features, target `features`
|
||||
[ ] Make sure to include one or more tests for your change
|
||||
[ ] Add yourself to `AUTHORS`
|
||||
[ ] Add a new entry to the `CHANGELOG` (choose any open position to avoid merge conflicts with other PRs)
|
||||
- [ ] Target: for bug or doc fixes, target `master`; for new features, target `features`
|
||||
- [ ] Make sure to include one or more tests for your change
|
||||
- [ ] Add yourself to `AUTHORS`
|
||||
- [ ] Add a new entry to the `CHANGELOG` (choose any open position to avoid merge conflicts with other PRs)
|
||||
|
|
Loading…
Reference in New Issue