Conversation
|
@atztogo Can you help or assign someone to help with some of the C errors like |
Codecov ReportBase: 64.00% // Head: 64.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## develop #215 +/- ##
========================================
Coverage 64.00% 64.00%
========================================
Files 18 18
Lines 1328 1328
========================================
Hits 850 850
Misses 478 478
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This part, I don't understand. What do you want? Have you met |
Signed-off-by: Cristian Le <[email protected]>
Signed-off-by: Cristian Le <[email protected]>
Signed-off-by: Cristian Le <[email protected]>
If we run |
Signed-off-by: Cristian Le <[email protected]>
lan496
left a comment
There was a problem hiding this comment.
Thank you so much for the quick fix! I confirm many warnings occur by running clang-tidy for all files, but it will be better to be addressed them in another PR.
Note for me: cmake-pre-commit-hooks creates a build directory (currently _build-pre-commit specified in .pre-commit-config.yaml) and compile_commands.json.
@atztogo I also think this PR is ready to be merged.
Yeah, it can also use the pre-configured build directories. I chose against it because it might not collect all source code, e.g. if it's build with |
Closes #213
Note that there are some pre-commit that have not been fixed.
(Currently depends on #214 because I didn't rebase that out)