-
It would be a **good practice** to enforce linter to detect/avoid things like pointed out in #24
-
-
- [ ] Implement unit tests
- [ ] Unit tests should automatically run on PR
- [ ] Implement code coverage
- [ ] Add build passing/failing badge to readme
- [ ] Implement some coding style enforceme…
-
One of the CI should run some static checks.
This is a good place to start : https://blog.kitware.com/static-checks-with-cmake-cdash-iwyu-clang-tidy-lwyu-cpplint-and-cppcheck/
-
from PR #64 , the ability to test compilation on MSVC + borland + mingw automatically would be nice.
- [ ] run diag_test binary for some internal tests
- [ ] run the subset of `ctest` tests that …
-
Hi,
I was trying to use this action in my **[internal](https://docs.github.com/en/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositor…
-
## Purpose
Setup a CI pipeline for Github and Jenkins. The goal is to integrate CI DevOps practice both for the project and for personal learning. This is to include code coverage, static analysis, a…
-
Some of these includes can be deleted, but I'm presuming the unused functions are for users of the library?
![Screenshot from 2022-02-03 12-20-19](https://user-images.githubusercontent.com/159608/1…
-
## Problem
As mentioned in the GitHub blog post below, Actions is currently transitioning from Node 16 to Node 20.
- https://github.blog/changelog/2023-09-22-github-actions-transitioning-fro…
-
We should improve the CI testing coverage by doing:
- [ ] switch to the official cmake action by github and add testing for multiple compile targets (Release, debug)
- [ ] DevSkim (code scanning)
-…