Add icon and release badge to README#28
Merged
Merged
Conversation
Put the Emailable mark inline in the README heading, with the icon SVG committed under assets/. Add a latest-release badge linked to the releases page. It uses include_prereleases since every published release is currently a prerelease; the default badge would otherwise show nothing.
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
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.
assets/.The release badge uses
include_prereleasesbecause every published release is currently a prerelease — the default shields.io badge only tracks stable releases and would render "no releases" for this repo. With the flag it shows the newest published tag (v0.3.0 today, and v0.4.0 once that draft is published).