Introduce Table for GitHub Badges #252
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
jimboid
approved these changes
Jan 20, 2026
Member
jimboid
left a comment
jimboid
left a comment
There was a problem hiding this comment.
Table looks much cleaner than a smattering of badges. Thanks for doing this!
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.
Summary
This PR updates the
README.mdto introduce a table for GitHub badges. The aim is to standardise badge presentation and improve readability so users can quickly assess the current status of the codebase at a glance.Changes
Introduce badge table
Remove redundant copyright notice
README.md, as this information is already maintained in theLICENSEdocument.Impact
README.md.