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.
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Add contribex to github template owners
**What this PR does / why we need it**:
The `.github/` folder doesn't have an OWNERS file. These templates fall under contribex, so this would add an OWNERS file to this folder.
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue
Shorten issue template.
**What this PR does / why we need it**:
As discussed on contrib-ex, this shortens the github issue template.
- Be more explicit about sending people to stackoverflow for support
- Add boilerplate for setting an issue as a bug or feature
- Add boilerplate for setting a SIG
- Cut out the rest for brevity.
Automatic merge from submit-queue
Update troubleshooting link in ISSUE_TEMPLATE.md
**What this PR does / why we need it**:
Since our troubleshooting page has been moved, we should update the issue template.
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
**Special notes for your reviewer**:
ref: #44434
**Release note**:
```release-note
NONE
```
- 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.
