Repository navigation
Keep categories and link sections in alphabetical order - #81
Merged
Merged
Conversation
fmt now sorts both groups by name as part of the canonical form of list.json, so CI enforces the order. Categories stay ahead of the link sections. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Categories rendered in the order they were added to
list.json, which read as random.FormatListnow sorts categories and link sections by name, case-insensitively, as part of the canonical form, sofmtreorderslist.jsonandfmt -checkin CI keeps it that way. Categories (repositories) stay ahead of link sections (documentation, books, videos, blog posts, podcasts); the two groups never mix.list.jsonis reordered in this PR. The README and site follow after the sync job regenerates them.🤖 Generated with Claude Code