Automatic code coverage testing in MRs
Once #80 (closed) is done, rig up the CI to use https://diff-cover.readthedocs.io to check that all new code will be covered by tests.
The code coverage results in cobertura.xml can be produced by Meson with gcovr, see weston!307 for instance.
That's easier said than done though, because we cannot require 100% coverage, there are always error paths etc. that are not triggered in tests. How to integrate with Gitlab is also a good question.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information