-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Badges for Semaphore #28
Comments
@vlasar We worked with @ackerdev to provide developers with a simple way to generate Shields themselves but that work is not anywhere near complet at the moment. That said we already built an |
@vlasar any update on this? The current Semaphore badge looks out-of-place compared to all the other "shielded" badges of other services. |
We have now added support for shields.io badges on Semaphore. Better late than never. Thank you. |
@stevelacey Are the Semaphore badges not defaulting to the right style? Do they rely on |
@espadrine https://semaphoreapp.com/api/v1/projects/eb289e04-3982-4de1-9e66-8436a67cf607/262663/shields_badge.svg?style=flat doesn't seem to do anything – they self-hosted – so need an update? Dunno – there's a few services with outdated badges though, see https://github.com/crysalead/kahlan |
Indeed. @vlasar do you have information on that? Do you need help? |
I'm no longer working on Semaphore, but I am trying to get in touch with them. cc @markoa |
Hi folks, it looks like it is now expected that shields.io is proxying the badge URLs to the CI service, while on Semaphore we're still hosting the images ourselves. What is the procedure to do it the proxy way? |
@markoa To avoid having to deal with image updates manually, the simplest way to do is to request the badge from shields.io at If you wish to continue to self-host those badges, you can of course download them from shields.io, and update them periodically. |
@espadrine Thanks for the explanation. I think we'll start requesting the badge from shields.io. Would it be useful to post here when we implement it? |
@markoa Yes! Definitely. |
@markos any progress on this? |
@stevelacey wrong person :) |
@markos well that's just unfair! :) |
We have updated our badges to match current design used by other services. Unfortunately because we're self-hosting them, optional params for themes are not supported yet, but in future we'll provide that option too. |
@rastasheep How about redirecting to shields.io (including the query string)? Then we'll have whatever customization shields.io offers. As well as they'll always match other shields badges on the same page (right now Semaphore badges are a slightly different size and text spacing to Shields.io). |
Hello,
I'm working on Semaphore and would like to get it "shielded".
We uses badges for the following build statuses:
Build badges from here:
![Shields Badges](https://camo.githubusercontent.com/e9ad9417d6fe2a11aca2d857e346f19468ac888d6408f0b9ed48433b75c190bf/68747470733a2f2f7261772e6769746875622e636f6d2f6f6c69766965726c6163616e2f736869656c64732f6d61737465722f736869656c64735f77686974652e706e67)
suite our color taste but we need a badge for the "unknown" status instead of the "error" status.
Could you create those badges for us or what is the standard workflow?
The text was updated successfully, but these errors were encountered: