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
I would like to avoid storing badges in my repository code. Ideally I would like to store my badges un der the GitHub Action execution itself. This way I can reference it in the markdown.
<Path to my Repository>/actions/workflows/myGitHubActionFile.yml/jacoco.svg
Is there a workaround for this?
The text was updated successfully, but these errors were encountered:
Otherwise, if you want a badge with "burnt-in" coverage percentage, things are more complicated. I've had the idea of storing rendered badges in artifacts, but that doesn't work (at least trivially) because there's no predictable way to link to the latest artifacts of a workflow. You'd also have to deal with the problem of artifact retention.
So I think currently there's no straight-forward way to achieve this without involving a third-party host to associate coverage percentage with a branch/commit-ish.
I think a convenient way would be to provide output variables which then can be picked up by another action to create a gist which then can be used to create a badge. This would be the most flexible and least "intrusive" way imho.
Hi,
I would like to avoid storing badges in my repository code. Ideally I would like to store my badges un der the GitHub Action execution itself. This way I can reference it in the markdown.
<Path to my Repository>/actions/workflows/myGitHubActionFile.yml/jacoco.svg
Is there a workaround for this?
The text was updated successfully, but these errors were encountered: