[Feature Request] Shields.IO Endpoint API #8839

New Issue

GiteaMirror · 2025-11-02T08:20:22-06:00

GiteaMirror commented

2025-11-02 08:20:22 -06:00

Originally created by @OdinVex on GitHub (Apr 18, 2022).

Shields.IO supports custom endpoints to return information for badges. It'd be pretty neat for Gitea to have an endpoint to query various info to support it.

Originally created by @OdinVex on GitHub (Apr 18, 2022). Shields.IO supports custom endpoints to return information for badges. It'd be pretty neat for Gitea to have an endpoint to query various info to support it.

GiteaMirror added the type/proposal label 2025-11-02 08:20:22 -06:00

GiteaMirror closed this issue

2025-11-02 08:20:23 -06:00

GiteaMirror commented

2025-11-02 08:20:23 -06:00

@techknowlogick commented on GitHub (Apr 18, 2022):

Could you provide some links for documentation on what would be needed?

@techknowlogick commented on GitHub (Apr 18, 2022): Could you provide some links for documentation on what would be needed?

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@OdinVex commented on GitHub (Apr 18, 2022):

Could you provide some links for documentation on what would be needed?

https://shields.io/endpoint

@OdinVex commented on GitHub (Apr 18, 2022): > Could you provide some links for documentation on what would be needed? https://shields.io/endpoint

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@techknowlogick commented on GitHub (Apr 22, 2022):

Thanks for providing that information. I think this would be better suited for a 3rd party middleware, or 1st party support within shields, as otherwise we'd be duplicating all our endpoints to provide information in a specific format.

@techknowlogick commented on GitHub (Apr 22, 2022): Thanks for providing that information. I think this would be better suited for a 3rd party middleware, or 1st party support within shields, as otherwise we'd be duplicating all our endpoints to provide information in a specific format.

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@6543 commented on GitHub (Apr 22, 2022):

-> https://github.com/badges/shields/issues/4040 etc...

@6543 commented on GitHub (Apr 22, 2022): -> https://github.com/badges/shields/issues/4040 etc...

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@OdinVex commented on GitHub (Apr 22, 2022):

Some things can't necessarily be queried by Shields.io, I'd also prefer an air-gapped situation. I disagree, but your project. Besides, it'd have only needed one endpoint, nothing more, nothing complicated.

@OdinVex commented on GitHub (Apr 22, 2022): Some things can't necessarily be queried by Shields.io, I'd also prefer an _air-gapped_ situation. I disagree, but your project. Besides, it'd have only needed one endpoint, nothing more, nothing complicated.

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@6543 commented on GitHub (Apr 23, 2022):

they have fully github support, and githup does not implement there api either - so they muse be a way to do so

PS: they can reuse most of the github code anyway as gitea mimic most endpoints

@6543 commented on GitHub (Apr 23, 2022): they have fully github support, and githup does not implement there api either - so they muse be a way to do so PS: they can reuse most of the github code anyway as gitea mimic most endpoints

GiteaMirror commented

2025-11-02 08:20:24 -06:00

@OdinVex commented on GitHub (Apr 23, 2022):

they have fully github support, and githup does not implement there api either - so they muse be a way to do so

PS: they can reuse most of the github code anyway as gitea mimic most endpoints

Implementing an endpoint can save a lot of bandwidth instead of requiring them to download entire pages to parse. I get the impression you might not know what endpoint I was talking about...a queryable API specifically for Shields.io...?

@OdinVex commented on GitHub (Apr 23, 2022): > they have fully github support, and githup does not implement there api either - so they muse be a way to do so > > PS: they can reuse most of the github code anyway as gitea mimic most endpoints Implementing an endpoint can save a lot of bandwidth instead of requiring them to download entire pages to parse. I get the impression you might not know what endpoint I was talking about...a queryable API specifically for Shields.io...?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8839