Auto-add team-X labels to issues opened through the bug / FR template + some clean up

PiperOrigin-RevId: 603410096
Change-Id: I74a6a8403cfd79f52bf434e81cdc1d364af6a505

Author: keertk

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -22,15 +22,13 @@ body:
   - type: dropdown
     id: subteam
     attributes:
-      label: >
-        Which category does this issue belong to?
-      description: >
-        Answering this will help us triage this issue faster and more accurately to the
-        relevant team(s).
+      label: Which category does this issue belong to?
+      description: Help us triage this issue faster and more accurately to the relevant team(s).
       multiple: true
       options:
         - Android
-        - C++/Objective-C Rules
+        - C++ Rules
+        - Objective-C Rules
         - CLI
         - Configurability
         - Core

.github/ISSUE_TEMPLATE/cherry_pick_request.yml

@@ -25,25 +25,23 @@ body:
         Which category does this issue belong to? Please select the corresponding label(s).
       multiple: true
       options:
-        - team-CLI
-        - team-OSS
-        - team-Core
-        - team-Bazel
         - team-Android
-        - z-team-Apple
-        - team-Rules-API
         - team-Rules-CPP
-        - team-Local-Exec
-        - team-Rules-Java
         - team-Rules-ObjC
+        - team-CLI
+        - team-Configurability
+        - team-Core
+        - team-Documentation
+        - team-ExternalDeps
+        - team-Rules-Java
         - team-Loading-API
+        - team-Local-Exec
+        - team-OSS
         - team-Performance
-        - team-Remote-Exec
-        - team-ExternalDeps
         - team-Rules-Python
+        - team-Remote-Exec
+        - team-Rules-API
         - team-Rules-Server
-        - team-Documentation
-        - team-Configurability
         - team-Starlark-Integration
         - team-Starlark-Interpreter
   - type: textarea

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -22,15 +22,13 @@ body:
   - type: dropdown
     id: subteam
     attributes:
-      label: >
-        Which category does this issue belong to?
-      description: >
-        Answering this will help us triage this issue faster and more accurately to the
-        relevant team(s).
+      label: Which category does this issue belong to?
+      description: Help us triage this issue faster and more accurately to the relevant team(s).
       multiple: true
       options:
         - Android
-        - C++/Objective-C Rules
+        - C++ Rules
+        - Objective-C Rules
         - CLI
         - Configurability
         - Core

.github/advanced-issue-labeler.yml

@@ -0,0 +1,43 @@
+---
+
+policy:
+  - template: [bug_report.yml, feature_request.yml]
+    section:
+      - id: [subteam]
+        label:
+          - name: team-Android
+            keys: ['Android']
+          - name: team-Rules-CPP
+            keys: ['C++ Rules']
+          - name: team-Rules-ObjC
+            keys: ['Objective-C Rules']
+          - name: team-CLI
+            keys: ['CLI']
+          - name: team-Configurability
+            keys: ['Configurability']
+          - name: team-Core
+            keys: ['Core']
+          - name: team-Documentation
+            keys: ['Documentation']
+          - name: team-ExternalDeps
+            keys: ['External Dependency']
+          - name: team-Rules-Java
+            keys: ['Java Rules']
+          - name: team-Loading-API
+            keys: ['Loading API']
+          - name: team-Local-Exec
+            keys: ['Local Execution']
+          - name: team-Performance
+            keys: ['Performance']
+          - name: team-Rules-Python
+            keys: ['Python Rules']
+          - name: team-Remote-Exec
+            keys: ['Remote Execution']
+          - name: team-Rules-API
+            keys: ['Rules API']
+          - name: team-Rules-Server
+            keys: ['Server-Side Rules']
+          - name: team-Starlark-Integration
+            keys: ['Starlark Integration']
+          - name: team-Starlark-Interpreter
+            keys: ['Starlark Interpreter']

.github/workflows/issue-labeler.yml

@@ -0,0 +1,37 @@
+---
+
+name: Issue labeler
+on:
+  issues:
+    types: [ opened ]
+
+jobs:
+  label-issues-policy:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+
+    strategy:
+      matrix:
+        template: [ bug_report.yml, feature_request.yml ]
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Harden Runner
+        uses: step-security/harden-runner@eb238b55efaa70779f274895e782ed17c84f2895 # v2.6.1
+        with:
+          egress-policy: audit
+
+      - name: Parse issue form
+        uses: stefanbuck/github-issue-parser@c1a559d78bfb8dd05216dab9ffd2b91082ff5324  # v3.0.1
+        id: issue-parser
+        with:
+          template-path: .github/ISSUE_TEMPLATE/${{ matrix.template }}
+
+      - name: Set labels based on policy
+        uses: redhat-plumbers-in-action/advanced-issue-labeler@6ee6fddfd744ee26b977e6a0436916f256896971  # v2.0.3
+        with:
+          issue-form: ${{ steps.issue-parser.outputs.jsonString }}
+          template: ${{ matrix.template }}
+          token: ${{ secrets.GITHUB_TOKEN }}