Repository navigation
Keep PR security fast and check before release - #14
Merged
Merged
Conversation
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
1 participant
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.
Security checks on PRs stay limited to the fast secret scan. Source analysis, production advisory checks and workflow analysis run at release/deployment or on demand. The release/deployment job depends on the security job; critical dependency/source findings and scanner failures stop publication. Noncritical findings require review. Automatic Socket checks are disabled through the supported repository configuration.
GitHub secret scanning and push protection are enabled separately. Existing code tests, coverage and compatibility CI keep their triggers.
Validation: workflow YAML, prerequisite/permission checks and offline zizmor passed. The pinned shared release workflow passed a hosted dependency, secret, workflow and CodeQL run. Repository-specific code checks were run where required; the remaining ordinary CI checks run on this PR.