This does not rely on img.shields.io, simplifies the workflow code, and remove the need for the noisy commits in capa-rules. We still need the commits in capa to sync the submodule. I'll send a PR in capa to use the new badge in a moment.
This requires giving the token gist persmissions, which I have already done. So it should work when we merge it.
We are using gist badges in VM-Packages since a few days, in case you want to see it working. We update the number of packages when adding a new package and the the daily package failures once a day.
This does not rely on
img.shields.io, simplifies the workflow code, and remove the need for the noisy commits in capa-rules. We still need the commits in capa to sync the submodule. I'll send a PR in capa to use the new badge in a moment.This requires giving the token gist persmissions, which I have already done. So it should work when we merge it.
We are using gist badges in VM-Packages since a few days, in case you want to see it working. We update the number of packages when adding a new package and the the daily package failures once a day.