Brian Gianforcaro 3b7d8ed6a5 Meta: Add actions work flow to run pvs-studio static analysis ... Much like the sonar cloud workflow, this workflow runs pvs-studio static analysis, and uploads the SARIF results to github. This is the most "convenient" way to publish results, but unfortunately users need write access to the repository to reach static analysis results rendered in github. As a work around folks can just look at the logs where issues are printed during analysis, this works reasonably well. In the future it might make sense to also render the results as HTML and publish them using github page, much like we do with man pages. I believe the pvs-studio plog-converter tool supports that as well. https://pvs-studio.com/en/docs/manual/0036/		2021-10-05 20:07:04 +00:00
..
cmake.yml	Meta: Switch to a SuperBuild that splits host and target builds	2021-09-15 19:04:52 +04:30
discord.yml	CI: Remove discord build status notifications	2021-06-18 13:45:18 +01:00
libjs-test262.yml	Meta+LibUnicode: Move unicode_data helper to Meta/CMake	2021-08-28 08:44:17 +01:00
lintcommits.yml	CI+Meta: Add Signed-off-by tag filter to the commit message linter	2021-09-07 20:46:34 +01:00
manpages.yml	CI: Run libjs-test262 and update results on every push to master	2021-06-05 19:27:55 +01:00
pvs-studio-static-analysis.yml	Meta: Add actions work flow to run pvs-studio static analysis	2021-10-05 20:07:04 +00:00
sonar-cloud-static-analysis.yml	Meta: Include source sha in sonarcloud analysis metadata	2021-10-02 18:16:15 +02:00
twitter.yml	CI: Disable variable substitution on input to the twitter script	2021-08-15 23:21:20 +04:30