GEMDAT uses GitHub Actions to generate a coverage badge, which is published to a GitHub Gist and from there can be included in the README.md. See https://github.com/GEMDAT-repos/GEMDAT/blob/main/.github/workflows/tests.yaml

Something like this could also perhaps be done for code quality.

This way, we could remove SonarCloud as an external dependency, which would simplify setup. Ideally, the action would be published separately, so that not every generated package has to maintain this workflow themselves, but that could be a next step as well.

It would also fix the issue in #221, because creating a badge doesn't have to be done in a PR, and that's the only place where the secret is necessary in the workflow.

@v1kko or @stefsmeets would you be interested in (helping) contributing this?