From a5b9332df4b04b42786c88052ff973d4d7565be7 Mon Sep 17 00:00:00 2001
From: Daniel Chalmers <moondpc@gmail.com>
Date: Sun, 26 Jul 2026 23:36:47 -0500
Subject: [PATCH] Triage new issues with AutoTriage

Issues opened here have gone unlabelled and unanswered for long stretches.
AutoTriage applies labels, asks for missing repro details, and retitles
unclear reports the moment an issue is opened, using the same action
MudBlazor/MudBlazor already runs.

Issues only, with no pull_request_target trigger: this repo does not see
enough external pull request traffic to justify one, and adding it would
mostly fire on bot pull requests.

The job is guarded on `repository_owner` so it does not run in forks, and on
`sender.type != Bot` so bot-opened issues such as Renovate dependency
dashboards are skipped. GEMINI_API_KEY is already an organization secret, so
no setup is required.
---
 .github/workflows/autotriage.yml | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 .github/workflows/autotriage.yml

diff --git a/.github/workflows/autotriage.yml b/.github/workflows/autotriage.yml
new file mode 100644
index 0000000..709be99
--- /dev/null
+++ b/.github/workflows/autotriage.yml
@@ -0,0 +1,24 @@
+name: AutoTriage
+
+on:
+  issues:
+    types: [opened]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  triage:
+    if: ${{ github.repository_owner == 'MudBlazor' && github.event.sender.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: danielchalmers/AutoTriage@v4
+        with:
+          issues: ${{ github.event.issue.number }}
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}