Triage new issues with AutoTriage - #49
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs the same AutoTriage action as
MudBlazor/MudBlazor, on newly opened issues only.Why: 11 of 12 open issues are over a year old, including #22 ("Instructions to get started don't work", Dec 2023) and #26 ("Test app does not launch"). Inflow is only 2 issues per 180 days — the problem isn't volume, it's that nothing looks at them on arrival.
Issues only, no
pull_request_target— 3 external PRs in 180 days doesn't justify it.Guards:
repository_owner == 'MudBlazor'(skips forks, where it would fail on the missing key) andsender.type != 'Bot'(skips Renovate dashboards).GEMINI_API_KEYis already an org secret, so no setup needed.No
AutoTriage.prompt— the action falls back to its default policy. Usescheckout@v7rather than the@v4elsewhere here. Adddry-run: "true"to review the plan before it acts.Replaces #48, which became unreopenable after a bad force-push.