StaticAnalysis
StaticAnalysis copied to clipboard
JacobDomagala
GitHub action performs static analysis on C++/Python code, flags issues, and posts comments directly on PRs.
I am seeing a ton of these messages in the output: `cppcheck: error: could not find any files matching the filter.` As in a run on my repo in the...
I see this in the workflow run output `:128: RuntimeWarning: 'src.static_analysis_cpp' found in sys.modules after import of package 'src', but prior to execution of 'src.static_analysis_cpp'; this may result in unpredictable...
Allow user to control which tool is being used (sometime cppcheck can take a long time to complete, so it could be useful to disable it)
What needs to be done: - Add PR comment for unit tests with result - Update `TestRepo` to contain proper code base and run a proper test there (dispatch workflow?)
Currently one can use either CMake or just lists of files for C++ static analysis. Let's see whether we can use User generated `compile_commands.json`
Metadata
Owner
Metadata
GitHub action performs static analysis on C++/Python code, flags issues, and posts comments directly on PRs.