Create our own coverage badge?

[dbrakenhoff]

We could consider creating our own coverage badge. This would create a badge based on a coverage workflow on github actions. This will be less feature rich than coveralls or codacy. If I understand correctly each test on github actions will overwrite a stored coverage report. The last report will be used to update a coverage.json file hosted on github gists. The badge will then use that file to create a badge through shields.io.

Idea found here: https://nedbatchelder.com/blog/202209/making_a_coverage_badge.html

Todo with @mbakker7 account:

• Create new secret gist (add file coverage.json with contents "{}")
• Copy gist ID to ci.yml under gistID
• Add github token with scope "gist" (https://github.com/settings/tokens), copy token to TTim secrets with name GIST_TOKEN

Do we want this or should we retry setting up codacy/coveralls?

[mbakker7]

If this makes life simpler, I am all for it.
Coveralls and codacy has always seemed somewhat magical. It isn't always clear to me what they measure and how they measure it.