security: org-wide secret scanning #129
Merged
Conversation
This file contains 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
geoffg-sentry
approved these changes
May 23, 2024
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.
Sentry uses GH's Secret Scanning on our public repositories, including their push protection to prevent secret leaks.
However, this does not cover private repositories without an expensive GHAS license. With this org-wide workflow, this will ensure secret scanning occurs on pull requests whether they're in a private or public repository.
This workflow does not pull the full commit history but just the current default branch + 2 commit to make sure scanning stays speedy. As a result, this won't detect secrets already committed to private repos, but we're working through any of those in a separate work stream.