[repo] Issue Triage WorkFlow#2879
Merged
Merged
Conversation
|
Repository collaborators can run the JMH benchmark suite against this PR by commenting: Optional regression threshold override (Δ% on Time or Alloc/op; defaults to 10%): Only one benchmark run per PR is active at a time — issuing a new |
Client V2 CoverageCoverage Report
Class Coverage
|
JDBC V2 CoverageCoverage Report
Class Coverage
|
JDBC V1 CoverageCoverage Report
Class Coverage
|
Client V1 CoverageCoverage Report
Class Coverage
|
TriageCategory: Summary What this impacts
Concerns
Required reviewer action
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
kavirajk
approved these changes
Jun 16, 2026
mshustov
reviewed
Jun 16, 2026
mshustov
reviewed
Jun 16, 2026
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 04706c1. Configure here.
mshustov
reviewed
Jun 16, 2026
mshustov
reviewed
Jun 16, 2026
mshustov
reviewed
Jun 16, 2026
mshustov
approved these changes
Jun 16, 2026
|
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
4 participants
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.
Summary
/triagein issue commentExample issues:
#2846
#2839
#2827 (comment)
Note
Medium Risk
Adds CI that runs a third-party model on untrusted issue text and needs
ANTHROPIC_API_KEY, though split jobs and tool restrictions reduce write/exfil risk; no runtime library code changes.Overview
Adds an automated GitHub issue triage path for maintainers: comment
/triageon an issue (or runworkflow_dispatchwith an issue number). Triage does not run on issue open, so random reporters cannot trigger model runs.New
.cursor/skills/triage-issues/defines a three-stage workflow (preview → local source research → standardized Triage Report with effort, type, module, labels, questions, and suggested tests).references.mdcaptures description sizing, minimal issue fields, module paths, and main/area:*labels.source-map.mdmaps v1/v2 client and JDBC modules,area:*→ directories, entry points, and stacktrace heuristics so triage stays offline and scoped..github/workflows/claude-issue-triage.ymlchecks out the repo, materializes the issue totriage/issue.md, runs Claude Code against the skill with Read/Glob/Grep/Write only (no Bash or web tools), and requirestriage/triage-report.md. A separatecommentjob downloads the artifact and posts or updates a sticky triage comment. The model job uses read-onlyGITHUB_TOKEN(issues: read); only the comment job getsissues: write, limiting prompt-injection impact on issue writes.Reviewed by Cursor Bugbot for commit f1af93f. Bugbot is set up for automated code reviews on this repo. Configure here.