superbyte-secret-scanning-maintainer

GitHub secret scanning alerts in comments and issue bodies are remediated by fetching location data, deleting or recreating affected comments, redacting secrets in place, and notifying authors. This workflow supports issue, PR, and discussion comments while maintaining audit trail integrity.

Secret redaction in GitHub discussion comments works by using GraphQL for discussion actions, redacting secrets in place or deleting affected comments, and ensuring secrets never appear in stdout or public comments. Edit history guidelines are preserved during redaction.

Multiple GitHub secret scanning alerts can be processed in a single workflow with per-location handling. It supports triaging and redacting secrets across issue comments, PR comments, discussion comments, issue bodies, and PR bodies simultaneously.

Triage and close GitHub secret scanning alerts in pull requests by fetching location data, redacting secrets in the PR body or comments, notifying the author with location-appropriate templates, and resolving the alert after remediation is complete.

When redacting secrets, GitHub issue bodies are redacted in place when possible, while comments may be deleted and recreated. Both approaches maintain audit trail integrity and ensure secrets are never exposed in stdout or public comments.