chore(ci): remove auto-triage claude workflow#135
Merged
Conversation
The auto-triage workflow has not been earning its keep. The recent debug run on issue #129 spent 38 turns and around a dollar of subscription quota before reporting that it could not access the issue body in any way it was allowed to: gh CLI is not installed on the runner, WebFetch is not in the allowlist, and the distillery KB search was using the wrong project name and returning zero results regardless of query. The workflow exited "success" because the SDK ran to completion, but no comment was ever posted and there is nothing useful to salvage from the session beyond Claude's own diagnostic. Coderabbit covers the PR review angle. The mention-gated claude.yaml stays for ad-hoc help, and scripts/claude-triage-dry-run.sh remains as a client-side preview if I ever want to run a triage prompt by hand. The triage-distillery.md prompt has no other consumer, so it goes too.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request removes the automated GitHub Actions-based issue triage system, deleting the triage prompt file and the associated workflow that previously performed AI-driven issue classification and analysis for newly opened or reopened issues. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Oddly
added a commit
that referenced
this pull request
Apr 13, 2026
Following on from #135, the rest of the Claude footprint goes too. The mention-gated claude.yaml worked in principle but I am not getting enough value out of it to justify the surface area, especially given the recent rate-limit pressure on the underlying subscription. The client-side dry-run script and its triage.md prompt have no consumer once the workflow is gone, so they go in the same commit. Coderabbit stays for PR review. The Claude GitHub App can be uninstalled from the repo at leisure — nothing in the tree depends on it any more.
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.
The auto-triage workflow has not been earning its keep. The recent debug run on #129 spent 38 turns and around a dollar of subscription quota before reporting it could not access the issue body in any allowed way: gh CLI is not installed on the runner, WebFetch is not in the allowlist, and the distillery KB search was using the wrong project name and returning zero results. The workflow exited "success" because the SDK ran to completion, but no comment was posted and there is nothing useful to salvage beyond Claude's own diagnostic.
Coderabbit covers the PR review angle. The mention-gated claude.yaml stays for ad-hoc help, and scripts/claude-triage-dry-run.sh remains as a client-side preview if I ever want to run the triage prompt by hand. The triage-distillery.md prompt has no other consumer, so it goes too.
This also implicitly reverts the show_full_output: true debug flag I landed in #134 — the file it was on is now gone.
Summary by CodeRabbit