Add Psalm Security Scanning#31
Closed
hunterjm wants to merge 3 commits into
Closed
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.
This pull request introduces a new GitHub Actions workflow to perform security scans using Psalm. The workflow is designed to run on pushes, pull requests to the
masterbranch, and on a scheduled weekly basis.New GitHub Actions workflow:
.github/workflows/psalm.yml: Added a new workflow named "Psalm Security Scan" to perform security scans using the Psalm GitHub Security Scan action. The workflow includes steps to checkout code, run the security scan, and upload the results to GitHub as SARIF files. It is triggered by pushes, pull requests to themasterbranch, and a weekly cron schedule.