Commit 8a80895
authored
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.1 parent f9b3706 commit 8a80895
4 files changed
Lines changed: 9 additions & 9 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -15,12 +15,12 @@ labels: "type-bug" | |||
| 15 | 15 | your problem has already been reported | |
| 16 | 16 | --> | |
| 17 | 17 | ||
| 18 | - **Bug report** | ||
| 18 | + # Bug report | ||
| 19 | 19 | ||
| 20 | 20 | A clear and concise description of what the bug is. | |
| 21 | 21 | Include a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example), if possible. | |
| 22 | 22 | ||
| 23 | - **Your environment** | ||
| 23 | + # Your environment | ||
| 24 | 24 | ||
| 25 | 25 | <!-- Include as many relevant details as possible about the environment you experienced the bug in --> | |
| 26 | 26 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -13,15 +13,15 @@ labels: "type-crash" | |||
| 13 | 13 | For CPython, a "crash" is when Python itself fails, leading to a traceback in the C stack. | |
| 14 | 14 | --> | |
| 15 | 15 | ||
| 16 | - **Crash report** | ||
| 16 | + # Crash report | ||
| 17 | 17 | ||
| 18 | 18 | Tell us what happened, ideally including a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example). | |
| 19 | 19 | ||
| 20 | - **Error messages** | ||
| 20 | + # Error messages | ||
| 21 | 21 | ||
| 22 | 22 | Enter any relevant error message caused by the crash, including a core dump if there is one. | |
| 23 | 23 | ||
| 24 | - **Your environment** | ||
| 24 | + # Your environment | ||
| 25 | 25 | ||
| 26 | 26 | <!-- Include as many relevant details as possible about the environment you experienced the bug in --> | |
| 27 | 27 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -4,6 +4,6 @@ about: Report a problem with the documentation | |||
| 4 | 4 | labels: "docs" | |
| 5 | 5 | --- | |
| 6 | 6 | ||
| 7 | - **Documentation** | ||
| 7 | + # Documentation | ||
| 8 | 8 | ||
| 9 | 9 | (A clear and concise description of the issue.) | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -4,16 +4,16 @@ about: Submit a proposal for a new CPython feature or enhancement | |||
| 4 | 4 | labels: "type-feature" | |
| 5 | 5 | --- | |
| 6 | 6 | ||
| 7 | - **Feature or enhancement** | ||
| 7 | + # Feature or enhancement | ||
| 8 | 8 | ||
| 9 | 9 | (A clear and concise description of your proposal.) | |
| 10 | 10 | ||
| 11 | - **Pitch** | ||
| 11 | + # Pitch | ||
| 12 | 12 | ||
| 13 | 13 | (Explain why this feature or enhancement should be implemented and how it would be used. | |
| 14 | 14 | Add examples, if applicable.) | |
| 15 | 15 | ||
| 16 | - **Previous discussion** | ||
| 16 | + # Previous discussion | ||
| 17 | 17 | ||
| 18 | 18 | <!-- | |
| 19 | 19 | New features to Python should first be discussed elsewhere before creating issues on GitHub, | |
0 commit comments