forked from orbit-oss/flask
update development resources
fix tox to test examples again add detox tox env for faster testing clean up makefile, add tox target add extra group for installing dev requirements clean up contributing doc, build with docs expand issue template add pull request template
This commit is contained in:
parent
a37f675ccb
commit
3c7625e8c0
8 changed files with 188 additions and 116 deletions
35
.github/ISSUE_TEMPLATE.rst
vendored
35
.github/ISSUE_TEMPLATE.rst
vendored
|
|
@ -1,2 +1,33 @@
|
|||
The issue tracker is a tool to address bugs.
|
||||
Please use the #pocoo IRC channel on freenode or Stack Overflow for questions.
|
||||
**This issue tracker is a tool to address bugs in Flask itself.
|
||||
Please use the #pocoo IRC channel on freenode or Stack Overflow for general
|
||||
questions about using Jinja or issues not related to Jinja.**
|
||||
|
||||
If you'd like to report a bug in Flask, fill out the template below. Provide
|
||||
any any extra information that may be useful / related to your problem.
|
||||
Ideally, create an [MCVE](http://stackoverflow.com/help/mcve), which helps us
|
||||
understand the problem and helps check that it is not caused by something in
|
||||
your code.
|
||||
|
||||
---
|
||||
|
||||
### Expected Behavior
|
||||
|
||||
Tell us what should happen.
|
||||
|
||||
```python
|
||||
Paste a minimal example that causes the problem.
|
||||
```
|
||||
|
||||
### Actual Behavior
|
||||
|
||||
Tell us what happens instead.
|
||||
|
||||
```pytb
|
||||
Paste the full traceback if there was an exception.
|
||||
```
|
||||
|
||||
### Environment
|
||||
|
||||
* Python version:
|
||||
* Flask version:
|
||||
* Werkzeug version:
|
||||
|
|
|
|||
16
.github/PULL_REQUEST_TEMPLATE.rst
vendored
Normal file
16
.github/PULL_REQUEST_TEMPLATE.rst
vendored
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
Describe what this patch does to fix the issue.
|
||||
|
||||
Link to any relevant issues or pull requests.
|
||||
|
||||
<!--
|
||||
Commit checklist:
|
||||
|
||||
* add tests that fail without the patch
|
||||
* ensure all tests pass with ``pytest``
|
||||
* add documentation to the relevant docstrings or pages
|
||||
* add ``versionadded`` or ``versionchanged`` directives to relevant docstrings
|
||||
* add a changelog entry if this patch changes code
|
||||
|
||||
Tests, coverage, and docs will be run automatically when you submit the pull
|
||||
request, but running them yourself can save time.
|
||||
-->
|
||||
Loading…
Add table
Add a link
Reference in a new issue