extend github "commits since" badge --> count from latest release

[tooomm]

Right now you need to provide a fixed tag to count from.
Can we have "latest" there as well, so it automatically counts from that and resets on release?

For example: https://img.shields.io/github/commits-since/SubtitleEdit/subtitleedit/latest.svg
instead having to update the badge tag every time since it's hard linked:
https://img.shields.io/github/commits-since/SubtitleEdit/subtitleedit/3.4.7.svg

[paulmelnikow]

Neat idea! Would you like to open a pull request?

[tooomm]

I can't help with code, sry. :(

[jtmoon79]

How do I use the latest feature of the commits since badge?

Using URL https://img.shields.io/github/commits-since/jtmoon79/goto_http_redirect_server/latest.svg the badge did not resolve to something meaningful (the badge reads no releases or repo not found).

Things I tried:

• add tag 0.7.3 and release 0.7.3 (this does resolve for URL https://img.shields.io/github/commits-since/jtmoon79/goto_http_redirect_server/0.7.3.svg)
• add tag latest and release latest that points to same commit as 0.7.3.

Still the URL .../latest.svg is never useful.

Project goto_http_redirect_server releases are here.

[tooomm]

I think you have only tags in your repo, no releases @jtmoon79

[jtmoon79]

Thanks for the reply @tooomm .

I think you have only tags in your repo, no releases

The project releases page counts 2 releases https://github.com/jtmoon79/goto_http_redirect_server/releases 🤔

[tooomm]

I can just tell that it works for me, but the release pages in the repo looks different: https://github.com/Cockatrice/Cockatrice/releases

-->
![](https://img.shields.io/github/commits-since/Cockatrice/Cockatrice/latest.svg)

[jtmoon79]

I can just tell that it works for me, but the release pages in the repo looks different:

Indeed! I poked around briefly: it's a github oddity!
AFAICT, project tags will also populate project releases if there are no project releases. So just by adding tags, there appears to be releases. But they are ... fake? ... releases. They are something not quite releases. It's confusing.
I created a project release from the project releases page. Works now.

Thanks for replying @tooomm

[calebcartwright]

I think the GitHub UX for releases is a fairly common source of confusion. I suspect this is because both tags and releases (if any exist) are listed in the default page, the "tags" tab filters down to releases-only but the "release" filters does not, not much visual distinction between the two especially for users that haven't worked with GH releases, etc.

For more info on the distinction: https://help.github.com/en/github/administering-a-repository/about-releases