Our current CI has a check for GCC warnings, but this is clearly not as deep as the tests done by clang tidy. I am adding a new CI step to check the code using clang tidy. Right now this will throw some warnings and errors which I will fix progressively.
Testing
This is actually adding tests, so I am using this PR as a testing environment.
Code related list:
[X] All in-code documentation related to this PR is up to date (Doxygen format)
[X] Lethe documentation is up to date
[X] New feature has unit test(s) (preferred) or application test(s), and restart files are in the generator folder
[X] The branch is rebased onto master
[X] Changelog (CHANGELOG.md) is up to date
[X] Code is indented with indent-all and .prm files (examples and tests) with prm-indent
Pull request related list:
[X] Labels are applied
[X] There are at least 2 reviewers (or 1 if small feature) excluding the responsible for the merge
[X] If this PR closes an issue or is related to a project, it is linked in the "Projects" or "Development" section
[X] If the fix is temporary, an issue is opened
[X] The PR description is cleaned and ready for merge
Description
Our current CI has a check for GCC warnings, but this is clearly not as deep as the tests done by clang tidy. I am adding a new CI step to check the code using clang tidy. Right now this will throw some warnings and errors which I will fix progressively.
Testing
This is actually adding tests, so I am using this PR as a testing environment. Code related list:
Pull request related list: