chore: sync governance files

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
-name: Bug Report
+name: Bug report
 description: File a bug report
 title: "[Bug]: "
-labels: ["type/bug"]
+labels: ["bug"]
 body:
   - type: markdown
     attributes:
@@ -36,15 +36,15 @@ body:
   - type: input
     id: host-arch
     attributes:
-      label: Host Arch
+      label: Host arch
       description: Which architecture are you using?
       placeholder: e.g. x86, ARM
     validations:
       required: true
   - type: input
     id: go-version
     attributes:
-      label: Go Version
+      label: Go version
       description: Which Go version are you using?
       placeholder: e.g. 1.18
     validations:
@@ -81,7 +81,7 @@ body:
   - type: textarea
     id: additional-information
     attributes:
-      label: Additional Information
+      label: Additional information
       description: |
         Any links or references to have more context about the issue.
 

.github/ISSUE_TEMPLATE/enhancement.yml

@@ -1,7 +1,7 @@
 name: Enhancement
 description: Suggest an enhancement
 title: "[Enhancement]: "
-labels: ["type/enhancement"]
+labels: ["enhancement"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature.yml

@@ -1,7 +1,7 @@
 name: Feature
 description: Suggest a new feature
 title: "[Feature]: "
-labels: ["type/feature"]
+labels: ["feature"]
 body:
   - type: markdown
     attributes:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,40 @@
+<!-- Type of change
+Please label this PR with one of the existing labels, depending on the scope of your change
+-->
+
+## What does this PR do?
+
+<!-- Mandatory
+Explain here the changes you made on the PR. Please explain the WHAT: patterns used, algorithms implemented, design architecture, etc.
+-->
+
+## Why is it important?
+
+<!-- Mandatory
+Explain here the WHY, or the rationale/motivation for the changes.
+-->
+
+## Related issues
+
+<!-- Recommended
+Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it.
+
+- Closes #123
+- Relates #123
+- Requires #123
+- Supersedes #123
+-->
+- 
+
+<!-- Recommended
+## How to test this PR
+
+Explain here how this PR will be tested by the reviewer: commands, dependencies, steps, etc.
+-->
+
+
+<!-- Optional
+## Follow-ups
+
+Add here any thought that you consider could be identified as an actionable step once this PR is merged.
+-->

.github/release-drafter.yml

@@ -6,6 +6,7 @@ template: |
 categories:
   - title: 🚀 Features
     labels:
+      - 'enhancement'
       - 'feature'
   - title: ⚠️ Breaking Changes
     labels:

.github/settings.yml

@@ -181,7 +181,7 @@ branches:
         # Required. Require branches to be up to date before merging.
         strict: true
         # Required. The list of status checks to require in order to merge into this branch
-        contexts: ["static-analysis", "tests (1.x, ubuntu-latest)"]
+        contexts: ["static-analysis", "test (1.x, ubuntu-latest)"]
       # Required. Enforce all configured restrictions for administrators. Set to true to enforce required status checks for repository administrators. Set to null to disable.
       enforce_admins: false
       # Prevent merge commits from being pushed to matching branches