Repository navigation
Improve GitHub status icons and installation instructions - #4
Merged
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
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.
Make the extension recognizable in Chrome and explain how to keep a release installed independently of a development checkout.
The Chrome Extensions page now uses the official Octicons GitHub mark. The toolbar uses the same silhouette in green for operational status, yellow for degradation/maintenance, red for partial/major outages, and gray for unknown/stale/failed checks. Tooltips and attention/unknown badges retain non-color information. Manifest assets cover 16/32/48/128px; toolbar assets cover 16/24/32px.
All PNGs are bundled locally. The Go standard-library generator recolors a checked-in raster mask derived from a pinned official SVG. Source provenance and the Octicons MIT license are included. Service-worker paths are rooted at the extension root, and storage/startup failures reset the icon to unknown.
The README now leads with release installation: choose a permanent folder (macOS example: ~/Applications/github-status-extension), download the runtime ZIP rather than source archives, extract with manifest.json at the selected folder's root, load it through chrome://extensions, and update the same folder using Reload. Other permanent locations are supported through Chrome's folder picker. Development/build instructions are separate. The guide follows Chrome's documented procedure and the local-build guidance used by Bitwarden and Stylus.
Validation: