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>
We now add the kind/regression to the PR template. We also put the kinds
into an HTML comment, because prow is now able to ignore those entries.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
With the merge of https://github.com/kubernetes/test-infra/pull/15040,
we're now able to use the kind/deprecation label for PRs as well. This
label will be consumed by the release notes generation tool.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
We are able to add further documentation to the release notes by parsing
an additional block at pull requests, for example:
```docs
- Description https://mylink.com
```
This commit adds this block to the pull request template.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
As the release process no longer requires an issue to be filed with each pull request, we should be treating pull requests as issues for the purposes of triage. This means it is helpful if PR authors add labels right as they open a PR.
- updated the headline
- updated the checklist numbers (was all "1.")
- converted the instructions into a markdown comment to make it
clearer what is an instruction.
