docs: add branded banner to the repo README - #10
Merged
Conversation
Bring the .github repo's own README in line with the sibling repos — open with the OneBrain <picture> banner (reusing the profile/assets/ SVGs), keeping the existing org-config content below.
kengio
force-pushed
the
docs/readme-banner
branch
from
July 3, 2026 11:45
fbfe0c2 to
40844ea
Compare
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
1 participant
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
Bring the
.githubrepo's own top-level README in line with the sibling repos — they all open with the OneBrain<picture>banner, this one didn't.README.md, reusing the existingprofile/assets/header-{dark,light}.svg(no new assets)Validated with the repo's own
check-links.py— the banner'ssrc/srcsetpaths resolve. (Pairs with the CI added in #9.)🤖 Generated with Claude Code