Closed MichaelHinrichs closed 1 month ago
Hey there!
Similar to what I mentionned in https://github.com/badges/shields/issues/10364#issuecomment-2230440078, all of the examples you listed are unlikely to change over time, I feel that these badges would be better served by a static badge rather than having to perform auth-based API calls. :)
If I have a look at the front page of https://appcenter.ms/ it says
Visual Studio App Center is scheduled for retirement on March 31, 2025
Aside from anything else, I think it would be poor use of someone's time to add badges for a service which is due to be retired in under a year.
the VS App Center logo, which I couldn't make work even though I know it's in simpleicons
There was previous an icon for this in the simple-icons set. However, all icons related to Microsoft products were removed in Simple Icons v13. There's more details on this in:
📋 Description
For Visual Studio App Center.
![Static Badge](https://img.shields.io/badge/service%20connection%20credentialType-credentials-CB2E6D?logo=VisualStudioAppCenter)
🔗 Data
https://openapi.appcenter.ms/#/account/sharedconnection_Connections Yes an API key is needed.
🎤 Motivation
visualize data about users, teams, team members, organizations, apps, and other things.