You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no need to write a JSON to send as data to shields.io. Instead you can create the SVG icon directly in the gist by generating the icon with the same node library that shields.io publishes. Then the url path to the icon in your README becomes a lot easier:
This adds the posibility of saving an SVG badge generated by the same
shields.io dirictly to the gist. Instead of prepering a JSON file to
be sent to their service, we use their library directly, which outputs
an SVG file that we can save to the user’s gist.
Filenames ending in `.svg` will use this library automatically.
Additionally there is a major refactoring where the older `node:http`
library has been swapped out for `fetch`.
Also swap from node 16 to node 20
fixesSchneegans#24
There is no need to write a JSON to send as data to shields.io. Instead you can create the SVG icon directly in the gist by generating the icon with the same node library that shields.io publishes. Then the url path to the icon in your README becomes a lot easier:
So I have a feature request: If the filename ends with
.svg
instead of.json
we can generate the icon and post the SVG straight to the gist.I have a proof of concept in a fork: https://github.com/runarberg/dynamic-badges-action
The text was updated successfully, but these errors were encountered: