ci(contract): add canonical secret-scan for claude-code parity (RFC internal#476 P1) #25
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "rfc476-p1-add-secret-scan"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RFC internal#476 finding #2. hermes already runs the inline canonical workspace-template validator but had NO secret-scan.yml while claude-code does (U2 universal secret-handling gate non-uniform). Adds the byte-identical canonical secret-scan.yml. Post-merge BP adds 'Secret scan / Scan diff for credential-shaped strings (pull_request)'.
Non-author review + devops-engineer merge. Additive.
Reviewed as non-author (core-qa). hermes already ran the inline canonical workspace-template validator; this PR adds ONLY the byte-identical canonical secret-scan.yml (U2 parity with claude-code, RFC internal#476 finding #2). Verified secret-scan.yml YAML parses + Secret scan job is the canonical regex set; all hermes CI contexts SUCCESS on push (validation + shell tests + publish-image). Additive, no existing gate touched. APPROVE.