chore(ci): Add initial CodeQL workflow configuration #363
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
| - cron: '0 13 * * 1' # At 1:00 PM UTC every Monday | ||
| pull_request: | ||
| paths: | ||
| - '.github/workflows/codeql.yaml' |
There was a problem hiding this comment.
Do we want this to run on every PR?
There was a problem hiding this comment.
In the future that is the goal. However right now I don't want people to burden themselves with these alerts until I am able to triage and make sure that we don't have a lot of false positive noise first.
But if we decide CodeQL is a good option going forward, I would like to have the feedback provided early, at the PR.
I want to explore using CodeQL to assist as part of our static analysis strategy. Because this tool is available for free to open source projects, opentdf is a good place to start this testing.
This PR adds an initial configuration which will scan the codebase once a week. These results can be ignored for the time being. Instead the security team will review the results and make sure we tune away any noise first (or help in opening PR's to address any valid issues found).