-
Notifications
You must be signed in to change notification settings - Fork 45
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
Badge should be reset for unchecked new versions #201
Comments
we have auto-detection of new releases in place does it match your expectations? |
Ah, ok. Makes sense to hold back builds to test something. The idea I tried to communicate is that the badge data should (automatically) be something like (color:orange, text:unverified) when a new version has been found but not yet reproduced (whatever the reason). Super idea in #202 btw. Cheers! |
any idea on how to trigger such a magic discovery and update of badge before auto-detection of new releases to do the rebuild? |
Oh, no magic. You already detect the new release, and when I created this issue, the table row entry for mada-style was empty (except for the version). Not that it should happen magically instantaneously on new releases in random projects 😀 |
How about this trick instead of magic; let the badge test include the tested version. Then viewers will know if it applies to latest release, regardless of auto detection scheduling. |
Such as this
Or repo owners (and users) will get a false sense of security.
The text was updated successfully, but these errors were encountered: