Repository navigation
Conversation
A rollup page that covers several providers listed Go modules and npm packages in one alphabetical run, which is hard to read and hides how much of a team's surface is in which language. Split the list under a heading per ecosystem, named the way someone would say it rather than by its identifier, so gomod reads as Go. Pages covering one ecosystem keep the flat list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Collaborator
Author
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
2 participants
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.
Stacked on #119, which gives a grouping one set of pages covering every provider. That means a team's page now lists Go modules and npm packages in one alphabetical run, which is harder to read than the per-provider pages it replaced.
This splits the list under a heading per ecosystem, with a count on each. Pages covering a single ecosystem keep the flat list, so nothing changes for a repo with one provider.
Headings are named the way someone would say them, so
gomodreads as Go andcargoas Rust.npmstays lowercase, which is why there's no uppercase styling on them.Checked on a generated pnpm + go site: a team owning one Go module and one npm package renders "Go (1)" and "npm (1)" with the right entries under each, and a team owning only npm packages renders as before.
Two geese and a duck are still three birds, but you'd want them in separate pens.