docs: improve repository presentation - #4
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
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.
The repository landing page did not expose its CI status, current npm version, or the provided project artwork, and the artwork would unnecessarily inflate the published package if kept under
docs/.This adds CI and npm version badges to the README, references the social preview from
.github/assets/social-preview.png, and keeps the image outside the npmfilestree. The GitHub About metadata and npm link are already aligned with the four supported harnesses.Verification:
npm run check-packagenpm pack --dry-rungit diff --check origin/main...HEADAgent: GPT-6 via Codex