@epezent this is an idea, probably cmake is more modern and clean solution.
CI using GitHub Actions offers workflows that can build the code in your repository and run your tests.
GitHub runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
More about "runners"... https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
@epezent this is an idea, probably cmake is more modern and clean solution.
CI using GitHub Actions offers workflows that can build the code in your repository and run your tests. GitHub runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure. More about "runners"... https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners
i.e. workflow run report in my fork