Repository navigation
fix(readme): make the platform-renames callout render on GitHub - #42
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.
Summary
GitHub only renders an alert when the
[!note]marker is alone on its line. The README callout had an Obsidian-style title on the same line, so GitHub showed it as plain text. The title now sits on its own bold line, and the rename list is broken into bullets. It renders on both GitHub and Obsidian.Only the top-level README changes, because it is the GitHub landing page. Topic files keep the Obsidian titled-callout convention from CLAUDE.md, since the guide is Obsidian-first.
🤖 Generated with Claude Code