Give Omegacode a plugin-owned Omega icon#2
Open
brsbl wants to merge 3 commits into
Open
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.
Summary
assets/icon.svgbb.branding.iconfield at that plugin-relative SVGThe stable package name (
bb-plugin-omega), plugin id (omega), screenshots, and runtime behavior are unchanged. Older bb 0.0.32 hosts continue to load the plugin and show their generic fallback. A host with the generic compact-icon contract renders the local SVG as a monochromecurrentColormask.The corresponding generic bb host commit is
fe46ef1c3onorigin/bb/plugin-owned-compact-icon; it has been handed tothr_4z84idik9afor the combined bb release. This PR does not require an Omegacode-specific host glyph.Validation
npm run check --workspace=bb-plugin-omeganpm run checknpm run hygieneomega, 13 packed files)git diff --checkA staged review loop found no P0-P2 issues. This PR must not be merged without explicit user approval.