Automatic issue triage on Gitea (Jev): kind and area labels, missing information, privacy and clinical-use flags

.gitea/ISSUE_TEMPLATE/bug_report.yaml

@@ -6,7 +6,7 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thank you for reporting. Please do **not** attach vendor files (IDAT, BPM, CSV, EGT, GTC) or any genetic data of real people.
+        Thank you for reporting. Please do **not** attach vendor files (IDAT, BPM, CSV, EGT, GTC) or any genetic data of real people. An automatic triage reads the text to suggest labels (see CONTRIBUTING.md).
   - type: input
     id: version
     attributes:

.gitea/workflows/issue_triage.yml

@@ -0,0 +1,19 @@
+# Gitea Actions workflow: automatic first triage of new issues (scripts/jev/issue_triage.py, TypeSafe Jev).
+# Needs the repository secret TYPESAFE_API_KEY; the built-in token applies labels and posts one comment.
+name: issue-triage
+on:
+  issues:
+    types: [opened, edited]
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Triage
+        env:
+          TYPESAFE_API_KEY: ${{ secrets.TYPESAFE_API_KEY }}
+          GITEA_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITEA_API: ${{ github.api_url }}
+          REPO: ${{ github.repository }}
+        run: python3 scripts/jev/issue_triage.py --event "$GITHUB_EVENT_PATH"