New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: A combined CRAN version and GitHub version badge #28
Comments
Cool. What's the underscore for? |
Sorry that was a typo. |
i like it |
I love the idea! I'm not sure if it's possible to add a space before the
|
That's exactly what I was writing, @karthik. I'm not sure it makes sense without the explanation. Can badges have dynamic tooltips? |
I don't think dynamic tooltips are possible on GH, but we can have a generic static one, i.e.
|
LGTM @gaborcsardi! |
I can also try to put a thin space around the |
Anyway, hopefully next week, after UseR I'll get to it! |
Bump @gaborcsardi! 🙏 |
Yes, sorry. Soon! |
shamelessly nudging a great idea! @gaborcsardi |
Well, obviously this hasn't happened. Unfortunately it is unlikely that it is going to happen, because I don't see a good way of getting the GH versions from GitHub.
So I am going to close it. Please open another issue if you have an idea of how this could be implemented. |
As discussed on Slack, we are trying to standardize READMEs across the rOpenSci project. In the interest of keeping badges concise and to prevent badge proliferation, we would humbly request a combined CRAN version/status + Github version badge.
Prototype:
@gaborcsardi mentioned that this would require an entirely new badge. If package is not on CRAN, then badge would reflect that.
Why? This badge would allow a potential user to quickly determine whether a package is on CRAN, and if development on GitHub has progressed considerably more than the last CRAN version. 🙏
The text was updated successfully, but these errors were encountered: