👍 Thank you @fhlasek

Can you update these facts as well:

• We moved away from using cpplint as the static code analyzer to clang-tidy.
  • The configuration settings for it are in the file .clang-tidy.
  • The command sequence to invoke it is:
    1. Export build commands using cmake. The configuration creates a compile-commands.json in the build folder.
       cmake -B build -S .
    2. Invoke clang-tidy
clang-tidy --fix --quiet -p build subfolder/file_to_check.cpp --
• Enable GitHub Actions on their respective folders
• GitHub Actions will execute clang-tidy and clang-format after every a push (not a commit). The result can create another commit if the actions made any changes on the author's behalf. Hence, it is better to wait and check the results of GitHub Actions after every push. If there were, better to call the command git pull to ensure the local codebase is synchronized with that on GitHub.

Let know if you need any further details.