Add team-triggered triage summaries to the Gemini issue triage workflow - #3
Open
divyashreepathihalli wants to merge 1 commit into
Open
Add team-triggered triage summaries to the Gemini issue triage workflow#3divyashreepathihalli wants to merge 1 commit into
divyashreepathihalli wants to merge 1 commit into
Conversation
jeffcarp
requested changes
Aug 28, 2026
| // Patterns for credentials that must never be echoed into a comment (or sent | ||
| // on to the model). Order matters: multi-line and specific patterns first, the | ||
| // generic high-entropy catch-all last. | ||
| const SECRET_PATTERNS = [ |
Member
There was a problem hiding this comment.
I don't think this is enough to protect against leaking data - I don't think we should move forward with this. Will add more review comments later.
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
2 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.
The reusable Gemini issue triage workflow now has two modes, chosen automatically from the caller's event:
Team member check
A commenter is authorized if their author_association is in allowed_associations (default OWNER,MEMBER,COLLABORATOR), or optionally if they belong to the org team named by triage_team (requires the new optional ORG_READ_TOKEN secret with read:org).
Add comment template
The comments will follow strict template for the response
Prompt-injection hardening
Every field except summary is a closed enum mapped through a lookup table; unknown values (including proto/constructor) fall back to fixed strings.
summary is redacted for credentials, stripped of backticks/angle brackets/control characters, collapsed to one line, capped at 600 chars, and rendered inside a ```text fence — so it can't break out, add links/HTML/images, or ping @mentions.
Related file paths come from the deterministic git grep step, regex-filtered; the trigger login is regex-validated.
Issue text and code snippets are wrapped in tagged blocks with an explicit untrusted-data instruction in the prompt.
Secret redaction
redactSecrets() masks Google/GitHub/AWS/sk-/Slack/Hugging Face tokens, Bearer headers, key=/password= assignments, emails, PEM private-key blocks, and long mixed alphanumeric blobs. It runs on the issue title/body and code snippets before they're sent to Gemini, and on the model summary before it's posted.