Repository navigation
test(web): build the fake API key fixture at runtime so gitleaks stops flagging - #517
Merged
Merged
Conversation
…s flagging promotions
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Same change as
3707d02ondev. The push-time gitleaks scan onmainchecks only the newest commit, so the squash promotion in #516 trippedgeneric-api-keyon the made-upak_live_...value inapps/web/test/dashboard-tabs.test.tsxand leftsecret-scanred onmain. The test now joins the value at runtime. Test-only; no runtime code changes.