Skip to content
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

GitHub release badge broken? #2017

Closed
PalatinCoder opened this issue Aug 29, 2018 · 2 comments
Closed

GitHub release badge broken? #2017

PalatinCoder opened this issue Aug 29, 2018 · 2 comments
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas

Comments

@PalatinCoder
Copy link

Hi everyone,
since a few days the Github release badge is broken for my repos, it shows release | repo not found.
package version seems to work fine for some repos, but not all of mine.

Is anyone experiencing the same problems?

@chris48s
Copy link
Member

chris48s commented Aug 29, 2018

Hi. thanks for reporting this. I can see that if I request this badge on a repo that has no releases e.g:

https://img.shields.io/github/release/PalatinCoder/DuttweilerApp.svg

or
https://img.shields.io/github/release/chris48s/arcgis2geojson.svg

I'm getting that result, although the badge is working normally for repos that have releases e.g:

https://img.shields.io/github/release/qubyte/rubidium.svg

It looks like the reason for this is that we're getting a 200 OK status code with a completely empty response from the GH api for repos which match this pattern e.g:

https://api.github.com/repos/PalatinCoder/DuttweilerApp/releases
https://api.github.com/repos/chris48s/arcgis2geojson/releases

but we're getting sensible responses for a repo with releases:

https://api.github.com/repos/qubyte/rubidium/releases

I'm not really familiar with the GH integrations as I've not done much work on them, so I'm not totally sure what we would normally expect that response to look like, but it seems unusual. Does anyone a bit more familiar with this have any thoughts?

@chris48s chris48s added the question Support questions, usage questions, unconfirmed bugs, discussions, ideas label Aug 29, 2018
@RedSparr0w
Copy link
Member

if you add /all to the end of your addresses it should work as expected:
https://img.shields.io/github/release/PalatinCoder/DuttweilerApp/all.svg

https://img.shields.io/github/release/chris48s/arcgis2geojson/all.svg

https://img.shields.io/github/release/qubyte/rubidium/all.svg

As without /all the api link returns 404 for the latest release:
https://api.github.com/repos/PalatinCoder/DuttweilerApp/releases/latest

Not sure if there is anyway we could work around this.


Closing as solved 👍

If this issue still persist or you feel it hasn't been resolved correctly please re-open this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas
Projects
None yet
Development

No branches or pull requests

3 participants