Closed coder3101 closed 4 years ago
Now, I will sync the PR, simulating a change and see if bot again spams or not.
As you can see the bot is not spamming by commenting the same thing again and again.
I will now change a few lines of tensor.hpp
so that new lines are also affected and for new lines updated in the source, the bot should again review and put only the new warnings, keeping the old warnings intact and without repeating.
The review fails if some compilation error occurs. As in this case!
Okay, now the compilation error has been fixed. Let me create a new member function rend2()
and the CI should report that the trailing return type should be used [modernize-use-trailing-return-type]
. 🤞
Okay finalized. Everything is working as expected.
@bassoy you can review this PR for what exactly a automated review by CI will look like!
The types of check to run is defined by this file named .clang-tidy in the root of ublas.
For your review and technical details as to how it is performed, here are the files that you should be looking into:
Closed in favor of #14
This is a review check PR. SHOULD NOT BE MERGED
Here is what should happen by automated review CI:
.clang-tidy
in the root of the project is used to configure which checks to run.For the test purpose, I formatted the
tensor.hpp
file and am proposing as PR nowThe review bot should come and put a clang-tidy review for that file changes. 🤞 (crossed fingers)