Move issue triage to triagebot-action#17114
Conversation
Replace three separate workflows and two Flue orchestration files with a single workflow that uses withastro/triagebot-action@v0.2.0. The action handles the full triage lifecycle internally: - Triage pipeline (reproduce, diagnose, verify, fix) - Fix verification (comment classification, PR creation) - Re-triage (new comment evaluation, label swap) - Branch cleanup on issue close Label names updated to use triage: prefix for the new FSM.
|
| Name | Type |
|---|---|
| astro | Patch |
| @test/astro-client-only-pkg | Patch |
| @test/before-hydration | Patch |
| @test/build-assets | Patch |
| @test/css-order-dynamic-import | Patch |
| @test/css-order-import | Patch |
| @test/css-order-layout | Patch |
| @test/css-order | Patch |
| @test/dont-delete-me | Patch |
| @test/lazy-layout | Patch |
| @test/multiple-jsx-renderers | Patch |
| @test/multiple-renderers | Patch |
| @test/prerender-conflict-dynamic-dynamic | Patch |
| @test/prerender-conflict-static-dynamic | Patch |
| @test/react-and-solid | Patch |
| @test/reexport-astro-containing-client-component | Patch |
| create-astro | Patch |
| @test/create-astro-not-empty | Patch |
| @astrojs/alpinejs | Patch |
| @astrojs/cloudflare | Patch |
| @astrojs/markdoc | Patch |
| @astrojs/mdx | Patch |
| @test/mdx-images | Patch |
| @test/mdx-infinite-loop | Patch |
| @test/mdx-namespace | Patch |
| @test/mdx-optimize | Patch |
| @test/mdx-page | Patch |
| @test/mdx-plus-react-errors | Patch |
| @test/mdx-plus-react | Patch |
| @test/mdx-env-variables | Patch |
| @astrojs/netlify | Patch |
| image-missing-dimention | Patch |
| @astrojs/node | Patch |
| @astrojs/preact | Patch |
| @astrojs/react | Patch |
| @fixture/react-19-preloads | Patch |
| @astrojs/solid-js | Patch |
| @astrojs/svelte | Patch |
| @astrojs/vercel | Patch |
| @astrojs/vue | Patch |
| astro-language-server-test | Patch |
| language-server-tests | Patch |
| @astrojs/markdown-satteri | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
Only GITHUB_TOKEN_BASE and gitPush are still used by the merge workflows. The rest were only used by the triage/verification workflows that are now handled by triagebot-action.
trueberryless
left a comment
There was a problem hiding this comment.
I really like this idea. Makes it also possible to use the new action in other repos in the ecosystem.
I left two little thoughts.
| gh issue comment "$ISSUE_NUMBER" --repo "$REPO" --body "Hello @${{ github.event.issue.user.login }}. Please provide a [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) using a GitHub repository or [StackBlitz](https://astro.new/repro). Issues marked with `needs repro` will be closed if they have no activity within 3 days." | ||
|
|
||
| gh issue edit "$ISSUE_NUMBER" --repo "$REPO" --remove-label "needs triage" | ||
| gh issue edit "$ISSUE_NUMBER" --repo "$REPO" --remove-label "triage: needs triage" |
There was a problem hiding this comment.
double triage in one label feels redundant. How about triage: needed?
There was a problem hiding this comment.
Ah, nvm, I see there is triage: needs repro as well...
Let's keep it that way then 👍
trueberryless
left a comment
There was a problem hiding this comment.
Nice, LGTM 🥳
I think both failing e2e tests are unrelated. Might be flaky or just need to upgrade this branch with changes from main (not sure which commit might have affected prefetch logic/tests)
Changes
I moved the code for issue triage over to https://github.com/withastro/triagebot-action so that:
Additionally I took the opportunity to make it into a full state machine, there are no more unknown states and the triage bot can recover from, for example, the reporter saying that the issue isn't fixed by the pending fix.
Also standardized the label names for consistency with
triage: {name}format.This PR removes the Flue code which now lives there, and uses the action.
Testing
Docs