We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should add a C++ linter, as #228 suggests. According to #228 (comment), the industry standard is clang-tidy.
clang-tidy
We should ensure that the dependencies for this are in our setup script, and that we add this to CI (or our end-to-end script in CI).
The text was updated successfully, but these errors were encountered:
What about this GItHub action? https://github.com/HorstBaerbel/action-clang-tidy
Sorry, something went wrong.
Applying this command fixes some things: clang-tidy --checks='modernize*, readability*' *.cpp --fix-errors
Does this mean we would apply C++ linting in the continuous integration?
Yes, we should enforce the C++ linting in GitHub Actions.
sven-oly
No branches or pull requests
We should add a C++ linter, as #228 suggests. According to #228 (comment), the industry standard is
clang-tidy
.We should ensure that the dependencies for this are in our setup script, and that we add this to CI (or our end-to-end script in CI).
The text was updated successfully, but these errors were encountered: