Repository navigation
fix(ci): allow the skills survey storage label in the secret scan [PANL-013] - #34
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bihc4e3Pg6Ago5K1xfMbe5
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
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.
Context
The weekly full-history secret scan has failed four Mondays in a row (Oct 5, 12, 19, 26), so main shows a red status on the repo page. It flags one line in an earlier version of the skills survey page:
var KEY = "ja-skills-survey-v1", a browser storage label, not a credential. Push and pull request scans stay green because they only read new changes. Ticket: PANL-013.Changes
One file,
.gitleaks.toml: the allowlist now also ignores the textja-skills-survey-v1, matched by text and not by commit hash so it survives squash merges. The existingYOUR_API_KEYallowance is unchanged. No other scan rule changes.Checks
python3 .github/scripts/safety_scan.py --range origin/main...HEADis cleanVerification after merge: trigger the workflow by hand on main and confirm the safety job passes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bihc4e3Pg6Ago5K1xfMbe5