Update github PR template.
+**How to categorize this PR?**
+<!--
+Please select area, kind, and priority for this pull request. This helps the community categorizing it.
+Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
+If multiple identifiers make sense you can also state the commands multiple times, e.g.
+ /area control-plane
+ /area auto-scaling
+ ...
+
+"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
+"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
+"/priority" identifiers: normal|critical|blocker
+
+-->
+/kind TODO
+/area os
+/os garden-linux
+/priority normal
+
**What this PR does / why we need it**:
**Which issue(s) this PR fixes**:
@@ -6,15 +25,16 @@ Fixes #
**Special notes for your reviewer**:
**Release note**:
-<!-- Write your release note:
+<!--
+Write your release note:
1. Enter your release note in the below block.
2. If no release note is required, just write "NONE" within the block.
Format of block header: <category> <target_group>
Possible values:
-- category: improvement|noteworthy|action
-- target_group: user|operator|developer
+- category: breaking|feature|bugfix|doc|other
+- target_group: user|operator|developer|dependency
-->
-```improvement operator
+```other operator
```
