Make add-comment risk dynamic based on content and confidence#3545
Open
mattleibow wants to merge 1 commit intomainfrom
Open
Make add-comment risk dynamic based on content and confidence#3545mattleibow wants to merge 1 commit intomainfrom
mattleibow wants to merge 1 commit intomainfrom
Conversation
Previously, all add-comment actions were hardcoded as 'high' risk regardless of content. This change makes the risk level dynamic: - low: factual content (repro findings, version matrix) with confidence >= 0.85 - medium: workaround/suggestion content with confidence >= 0.85 - high: close/reject content, or confidence < 0.70 Updated in both triage and repro schema cheatsheets and schema definitions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
mattleibow
added a commit
that referenced
this pull request
Mar 4, 2026
Re-evaluated all 64 add-comment actions across 114 cached JSON files using the new dynamic risk calculation from PR #3545: - 29 triage comments: high -> medium (workaround/suggestion content) - 5 triage comments: high -> low (factual content, high confidence) - 5 repro comments: low/medium -> high (paired with close actions) - 2 repro comments: low -> medium (non-factual, moderate confidence) - 1 repro comment: medium -> low (factual, high confidence) - 27 unchanged (correctly high: close-paired or reject language) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Previously, all
add-commentactions in triage and repro JSON outputs were hardcoded ashighrisk regardless of content. This made the risk field meaningless for comments — every comment required human review equally.Changes
Updated the
add-commentrisk from a static mapping to a dynamic calculation based on content type and confidence score:Files changed
.github/skills/issue-triage/references/schema-cheatsheet.md— replaced static table with decision table.github/skills/issue-repro/references/schema-cheatsheet.md— added decision table.github/skills/issue-triage/references/triage-schema.json— updated actionRisk description.github/skills/issue-repro/references/repro-schema.json— updated actionRisk descriptionImpact on existing cached JSON
Applying this to all 114 existing cached JSON files: