Skip to content
Snippets Groups Projects
Unverified Commit 8a808952 authored by Mariatta Wijaya's avatar Mariatta Wijaya Committed by GitHub
Browse files

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.
parent f9b3706d
Branches
Tags
No related merge requests found
......@@ -15,12 +15,12 @@
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 -->
......
......@@ -13,15 +13,15 @@
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 -->
......
......@@ -4,6 +4,6 @@
labels: "docs"
---
**Documentation**
# Documentation
(A clear and concise description of the issue.)
......@@ -4,16 +4,16 @@
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,
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment