Caleb Cartwright

Thanks for letting us know! I've opened an [issue upstream with the Security Headers](https://github.com/securityheaders/securityheaders-bugs/issues/110) folks as there's really nothing we can do from our end. It seems the new mandatory...

For anyone not subscribed to the upstream issue, it does sound like they'll be willing to work with us so we'll collaborate off GitHub and post updates back here once...

> @calebcartwright - in terms of the concept (i.e: "do we think this feature is a good idea?", as opposed to "is this good code?"), what are your views on...

> Any other maintainers have a view on this? I've a mild preference for `?logoSize=auto`

Recognize this has some conflicts that would be blockers, but in general, where did we land as far as our target strategic direction with this one?

> > where did we land as far as our target strategic direction with this one? > > My last comment was > > > add the `logoSize=auto` param as...

Seems CI is still rather unhappy. One is just the linter, and a quick `npm run prettier` should fix, but the others failing jobs have test failures, e.g.: https://github.com/badges/shields/actions/runs/6156362420?pr=9191 >...

Hi @6543! Can you provide some more detail on the intent of this issue? Are you requesting a new badge be supported in Shields, to provide a Release Version badge...

Thanks! Could you also provide info for the following questions/items: - Is there a public API? - Does the API require an API key? - Link to the API documentation.

> but i think gitea is worth adding to the official api I agree. It makes it easier for others to leverage the badge without having to include those long...