Users can opt in to selecting any of the following badges. Limit to 5 badges, so that they can choose the 5 that are most relevant for their tool. These would be presented as options during the onboarding process that they can “check off” to include.
Dynamic Badges (i.e., Auto-updating)
Code coverage from codecov.io. Example for nmfs-fish-tools/SSMSE:
Badges from github actions for a single run (or other CI). Example for the call-r-cmd workflow on SSMSE
All checks passing, GitHub actions:
Downloads for latest release (note that this is for exes, downloads will likely be 0 for r pkgs)
GitHub stars
GitHub release (latest by date)
GitHub last commit
GitHub release date
GitHub contributors
Static Badges
Indicator of published elsewhere: badge for publication (doi #?), zenodo, CRAN, or r open sci badge.
Here's an idea of how this could look:
Optional Badges
Users can opt in to selecting any of the following badges. Limit to 5 badges, so that they can choose the 5 that are most relevant for their tool. These would be presented as options during the onboarding process that they can “check off” to include.
Dynamic Badges (i.e., Auto-updating)
Static Badges