Shields: Improve usability for github releases when no releases present

Created on 16 Jan 2019  路  2Comments  路  Source: badges/shields

See #2785 #2017 and I seem to recall its coming up before, too.

  1. We could change the error to no releases or repo not found.
  2. We could add some documentation for the modal popup. It's kind of perfect for a badge-specific FAQ like this.
service-badge

Most helpful comment

I believe number two is the better option (or a combination of both). It's not abundantly clear, at least for me it wasn't, that when you push a tag you're not also pushing a new release. New tags show up in the repository releases tab and even show up as a release count from the main repository page.

All 2 comments

I believe number two is the better option (or a combination of both). It's not abundantly clear, at least for me it wasn't, that when you push a tag you're not also pushing a new release. New tags show up in the repository releases tab and even show up as a release count from the main repository page.

It's not abundantly clear, at least for me it wasn't, that when you push a tag you're not also pushing a new release.

I support this!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Turnerj picture Turnerj  路  3Comments

bruno-garcia picture bruno-garcia  路  3Comments

chadwhitacre picture chadwhitacre  路  4Comments

rominf picture rominf  路  3Comments

techtonik picture techtonik  路  3Comments