feat: Add shields.io endpoint badge API #261
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR also helps address the desire for customizable badge styles, as raised in issue #245. By exposing a shields.io compatible endpoint, this change will allow users to generate badges with their preferred styling. For example, a URL like (Note: The example URL will only become active once this PR is merged and the endpoint is deployed.) Furthermore, this PR lays the groundwork for potential native integration with shields.io in the future, which could lead to even simpler badge URLs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request re-implements the feature originally proposed in PR #122 by @dnaka91.
Due to the time passed and subsequent changes in the codebase, the original PR became difficult to merge. This new PR builds upon that foundation to bring the feature to fruition.
Many thanks to @dnaka91 for their excellent initial work and for identifying this valuable approach. Without their pioneering efforts, we wouldn't have discovered this effective way to integrate with shields.io.