docs: make README badge copy more general#479
Open
MackDing wants to merge 1 commit into
Open
Conversation
Author
|
Quick follow-up: this PR still appears clean and mergeable from my side. Happy to make any maintainer-preferred tweak if needed. |
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\n- update the README badge intro copy to say projects are using Sourcery, instead of using Sourcery to refactor\n\n## Why\nThe README now presents Sourcery more broadly as an AI code reviewer and IDE assistant, so the badge section's wording is a bit narrower than the rest of the page. This small docs tweak keeps that copy aligned without changing the badge itself.\n\n## Verification\n- verified the README now reads: "Let the world know your project is using Sourcery with this badge:"