Oliver Stöneberg

The template seems to do that. The GitHub Actions also aren't "free" either. There's a certain amount of minutes you can use each month without paying.

A workaround is using `--max-configs=1` in the command-line parameters. This will greatly improve the scan times for files with a lot of detected configuration.

If there's too many configuration Cppcheck will bail out and only check at most what is configured via `--max-configs` (default is 12) anyways: ``` Too many #ifdef configurations - cppcheck...

I contacted JetBrains about this and got a contact regarding CLion plugin development. Hopefully I will get some input on this soon.

To get the project configurations it is necessary to use CLion-specific functionality. I haven't figured out yet how to develop with them. There also were some recent changes outlined in...

If we have access to the build path (I know we can access the workspace path) we could leverage a potentially existing `compile_commands.json` to get the configuration. Maybe this could...

To get the project configurations it is necessary to use CLion-specific functionality. I haven't figured out yet how to develop with them. There also were some recent changes outlined in...

If we have access to the build path (I know we can access the workspace path) we could leverage a potentially existing `compile_commands.json` to get the configuration. Maybe this could...

It seems if you select a folder it will process the whole folder on the filesystem and not just the project files in that folder which may lead to unexpected...

I am planning on making the configuration regarding the `--language=` option a bit easier for 1.6.0 by handling it internally. The enhanced error balloon should probably also help in some...