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.
This commit is contained in:
Mariatta Wijaya 2022-07-22 09:19:08 -07:00 committed by GitHub
parent f9b3706df6
commit 8a808952a6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 9 additions and 9 deletions

View File

@ -15,12 +15,12 @@ labels: "type-bug"
your problem has already been reported your problem has already been reported
--> -->
**Bug report** # Bug report
A clear and concise description of what the bug is. A clear and concise description of what the bug is.
Include a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example), if possible. 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 --> <!-- Include as many relevant details as possible about the environment you experienced the bug in -->

View File

@ -13,15 +13,15 @@ labels: "type-crash"
For CPython, a "crash" is when Python itself fails, leading to a traceback in the C stack. 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). 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. 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 --> <!-- Include as many relevant details as possible about the environment you experienced the bug in -->

View File

@ -4,6 +4,6 @@ about: Report a problem with the documentation
labels: "docs" labels: "docs"
--- ---
**Documentation** # Documentation
(A clear and concise description of the issue.) (A clear and concise description of the issue.)

View File

@ -4,16 +4,16 @@ about: Submit a proposal for a new CPython feature or enhancement
labels: "type-feature" labels: "type-feature"
--- ---
**Feature or enhancement** # Feature or enhancement
(A clear and concise description of your proposal.) (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. (Explain why this feature or enhancement should be implemented and how it would be used.
Add examples, if applicable.) Add examples, if applicable.)
**Previous discussion** # Previous discussion
<!-- <!--
New features to Python should first be discussed elsewhere before creating issues on GitHub, New features to Python should first be discussed elsewhere before creating issues on GitHub,