fix(triage): Gate low-value issue comments#7
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
sentry-flue-agents | b352b79 | Jun 20 2026, 07:02 PM |
Teach issue triage to avoid standalone comments when Pierre has no useful addition, while passing reporter context so trusted maintainers and outside contributors can take different paths. Keep unsafe close fallback comments workflow-owned and extend eval fixtures to assert no-comment behavior for clear member-authored issues. Co-Authored-By: Codex <codex@openai.com>
dcramer
force-pushed
the
codex/triage-comment-gating
branch
from
85bcba1 to
b352b79
Compare
dcramer
changed the title
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.
Issue triage now has a clearer no-comment path when Pierre has no useful addition. The skill instructions tell the model not to post acknowledgment, praise, or restatement comments, and the workflow passes normalized reporter context so member, owner, collaborator, and outside-contributor reports can take different paths.
For trusted reporter issues, standalone comments now need structured intent: either a blocking missing-info request or a concrete repository validation finding. The unsafe-close path also uses a workflow-owned fallback comment instead of inspecting generated prose, and the issue-triage eval harness can assert
should_comment/comment_kindexpectations with reporter context. This covers the two observed low-value comments with regression fixtures while still allowing useful asks and validation notes.Validated with
pnpm run test,pnpm run typecheck, andpnpm run build.pnpm run evalswas attempted but could not run locally becauseOPENROUTER_API_KEYis not set and.env.localis absent.