Skip to content

Commit

Permalink
Use markdown headers instead of bold text for PR template
Browse files Browse the repository at this point in the history 
The usage of markdown headers will provide a more eye-friendly
formatting without having a need to add additional newlines to the PR.
This is reasoned by the GitHub markdown parser which adds additional
space before and after the header.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
  • Loading branch information
@saschagrunert
saschagrunert committed Nov 30, 2020
1 parent c1f36fa commit d0a3ecf
Show file tree
Hide file tree
Showing 5 changed files with 25 additions and 25 deletions.
10 changes: 5 additions & 5 deletions .github/ISSUE_TEMPLATE/bug-report.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,15 @@ If the matter is security related, please disclose it privately via https://kube
-->


**What happened**:
#### What happened:

**What you expected to happen**:
#### What you expected to happen:

**How to reproduce it (as minimally and precisely as possible)**:
#### How to reproduce it (as minimally and precisely as possible):

**Anything else we need to know?**:
#### Anything else we need to know?:

**Environment**:
#### Environment:
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
Expand Down
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/enhancement.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,6 @@ labels: kind/feature
---
<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:
#### What would you like to be added:

**Why is this needed**:
#### Why is this needed:
12 changes: 6 additions & 6 deletions .github/ISSUE_TEMPLATE/failing-test.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@ labels: kind/failing-test

<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->

**Which jobs are failing**:
#### Which jobs are failing:

**Which test(s) are failing**:
#### Which test(s) are failing:

**Since when has it been failing**:
#### Since when has it been failing:

**Testgrid link**:
#### Testgrid link:

**Reason for failure**:
#### Reason for failure:

**Anything else we need to know**:
#### Anything else we need to know:
12 changes: 6 additions & 6 deletions .github/ISSUE_TEMPLATE/flaking-test.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,16 @@ labels: kind/flake

<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI -->

**Which jobs are flaking**:
#### Which jobs are flaking:

**Which test(s) are flaking**:
#### Which test(s) are flaking:

**Testgrid link**:
#### Testgrid link:

**Reason for failure**:
#### Reason for failure:

**Anything else we need to know**:
#### Anything else we need to know:
- links to go.k8s.io/triage appreciated
- links to specific failures in spyglass appreciated

<!-- Please see the deflaking doc (https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/flaky-tests.md) for more guidance! -->
<!-- Please see the deflaking doc (https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/flaky-tests.md) for more guidance! -->
12 changes: 6 additions & 6 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-k
5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
-->

**What type of PR is this?**
#### What type of PR is this?

<!--
Add one of the following kinds:
Expand All @@ -26,19 +26,19 @@ Optionally add one or more of the following kinds if applicable:
/kind regression
-->

**What this PR does / why we need it**:
#### What this PR does / why we need it:

**Which issue(s) this PR fixes**:
#### Which issue(s) this PR fixes:
<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
-->
Fixes #

**Special notes for your reviewer**:
#### Special notes for your reviewer:

**Does this PR introduce a user-facing change?**:
#### Does this PR introduce a user-facing change?
<!--
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Expand All @@ -50,7 +50,7 @@ For more information on release notes see: https://git.k8s.io/community/contribu
```

**Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.**:
#### Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

<!--
This section can be blank if this pull request does not require a release note.
Expand Down

0 comments on commit d0a3ecf

Please sign in to comment.