summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2021-05-09 12:14:42 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2021-05-09 12:14:42 -0400
commitf8bb1c102258c321769edaa3daaa3eb73a135877 (patch)
tree5ddb6b9abbe5d8065a3023bf048a5915663660f9
parentccf1e5a0b1f1b6dcf717b4dcee894f2c61513bc9 (diff)
downloadsqlalchemy-f8bb1c102258c321769edaa3daaa3eb73a135877.tar.gz
formatting
Change-Id: I69092dc6c2121bb780aed1b145ccd3eaabb0ff5d
-rw-r--r--.github/ISSUE_TEMPLATE/bug_report.md5
1 files changed, 1 insertions, 4 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 6c8c8052b..f7e4fad36 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -13,14 +13,11 @@ If you are new to SQLAlchemy bug reports, please review our many examples
of [well written bug reports](https://github.com/sqlalchemy/sqlalchemy/issues?q=is%3Aissue+label%3A%22great+mcve%22). Each of these reports include the following features:
1. a **succinct description of the problem** - typically a line or two at most
-2. **code to reproduce the problem**, otherwise known as
- a [Minimal, Complete, and Verifiable](http://stackoverflow.com/help/mcve)
- example.
+2. **succinct, dependency-free code which reproduces the problem**, otherwise known as a [Minimal, Complete, and Verifiable](http://stackoverflow.com/help/mcve) example.
3. **complete stack traces for all errors**
4. Other things as applicable: **SQL log output**, **database backend and DBAPI driver**,
**operating system**, **comparative performance timings** for performance issues.
-
**Describe the bug**
<!-- A clear and concise description of what the bug is. -->