
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>
2.9 KiB
2.9 KiB
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: