summaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE
diff options
context:
space:
mode:
authorMariatta Wijaya <Mariatta@users.noreply.github.com>2022-07-22 16:19:08 (GMT)
committerGitHub <noreply@github.com>2022-07-22 16:19:08 (GMT)
commit8a808952a61b4bd572d95f5efbff1680c59aa507 (patch)
tree001e85c0f5cd065dbe2cfcad34523392fff5402c /.github/ISSUE_TEMPLATE
parentf9b3706df65c4962646587b437a4eb39289dfd4c (diff)
downloadcpython-8a808952a61b4bd572d95f5efbff1680c59aa507.zip
cpython-8a808952a61b4bd572d95f5efbff1680c59aa507.tar.gz
cpython-8a808952a61b4bd572d95f5efbff1680c59aa507.tar.bz2
Use Markdown Headers in GitHub Issue templates (GH-95111)
The Issue templates are using the markup to make text bold. We should be using proper text headers instead. I replaced the **bold** text markup with L1 headers.
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r--.github/ISSUE_TEMPLATE/bug.md4
-rw-r--r--.github/ISSUE_TEMPLATE/crash.md6
-rw-r--r--.github/ISSUE_TEMPLATE/documentation.md2
-rw-r--r--.github/ISSUE_TEMPLATE/feature.md6
4 files changed, 9 insertions, 9 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
index 7bdca21..1d93e07 100644
--- a/.github/ISSUE_TEMPLATE/bug.md
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -15,12 +15,12 @@ labels: "type-bug"
your problem has already been reported
-->
-**Bug report**
+# Bug report
A clear and concise description of what the bug is.
Include a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example), if possible.
-**Your environment**
+# Your environment
<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
diff --git a/.github/ISSUE_TEMPLATE/crash.md b/.github/ISSUE_TEMPLATE/crash.md
index 28d7bfe..dad3423 100644
--- a/.github/ISSUE_TEMPLATE/crash.md
+++ b/.github/ISSUE_TEMPLATE/crash.md
@@ -13,15 +13,15 @@ labels: "type-crash"
For CPython, a "crash" is when Python itself fails, leading to a traceback in the C stack.
-->
-**Crash report**
+# Crash report
Tell us what happened, ideally including a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example).
-**Error messages**
+# Error messages
Enter any relevant error message caused by the crash, including a core dump if there is one.
-**Your environment**
+# Your environment
<!-- Include as many relevant details as possible about the environment you experienced the bug in -->
diff --git a/.github/ISSUE_TEMPLATE/documentation.md b/.github/ISSUE_TEMPLATE/documentation.md
index 669c92a..174fd39 100644
--- a/.github/ISSUE_TEMPLATE/documentation.md
+++ b/.github/ISSUE_TEMPLATE/documentation.md
@@ -4,6 +4,6 @@ about: Report a problem with the documentation
labels: "docs"
---
-**Documentation**
+# Documentation
(A clear and concise description of the issue.)
diff --git a/.github/ISSUE_TEMPLATE/feature.md b/.github/ISSUE_TEMPLATE/feature.md
index 635ea43..ed051e9 100644
--- a/.github/ISSUE_TEMPLATE/feature.md
+++ b/.github/ISSUE_TEMPLATE/feature.md
@@ -4,16 +4,16 @@ about: Submit a proposal for a new CPython feature or enhancement
labels: "type-feature"
---
-**Feature or enhancement**
+# Feature or enhancement
(A clear and concise description of your proposal.)
-**Pitch**
+# Pitch
(Explain why this feature or enhancement should be implemented and how it would be used.
Add examples, if applicable.)
-**Previous discussion**
+# Previous discussion
<!--
New features to Python should first be discussed elsewhere before creating issues on GitHub,