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
Since we use the onlabel_CRAN_checks workflow on label of pull requests we end up with a status badge on the homepage of the package that indicates the status for some pull request and not for a version we would like to display.
The check should either indicate the state when running on main or on the latest release-x.y.z branch that has a published tag.
Since the workflow runs on pull requests, it never runs on main directly.
What we could do it so simply update the URI for the badge in the README.md when we create a new release-x.y.z pull request, much like we already do when updating the NEWS.md file.
When we then publish the version by merging the pull request the badge in the README.md will points to the outcome of the latest onlabel_CRAN_checks on the branch release-x.y.z of the latest release.
The text was updated successfully, but these errors were encountered:
j-i-l
changed the title
![On Label CRAN Checks](https://github.com/furrer-lab/abn/actions/workflows/onlabel_CRAN_checks.yml/badge.svg)](https://github.com/furrer-lab/abn/actions/workflows/onlabel_CRAN_checks.yml) always picks up the latest run
The status badge for onlabel_CRAN_checks always picks up the latest run
Jul 16, 2024
Since we use the
onlabel_CRAN_checks
workflow on label of pull requests we end up with a status badge on the homepage of the package that indicates the status for some pull request and not for a version we would like to display.The check should either indicate the state when running on
main
or on the latestrelease-x.y.z
branch that has a publishedtag
.Since the workflow runs on pull requests, it never runs on
main
directly.What we could do it so simply update the URI for the badge in the README.md when we create a new
release-x.y.z
pull request, much like we already do when updating the NEWS.md file.When we then publish the version by merging the pull request the badge in the README.md will points to the outcome of the latest
onlabel_CRAN_checks
on the branchrelease-x.y.z
of the latest release.The text was updated successfully, but these errors were encountered: