Repository navigation
chore: prepare version 1.0.3 - #96
Merged
Merged
Conversation
A reader who checks maturity asks who maintains the gem, how a release is published, and what they keep if maintenance stops. One page now answers these questions and asks for more maintainers. The README, the versioning page, and the comparison pages link to the new page and no longer state a count of maintainers. A new test fails when a page states one.
|
Docs7 for cardmagic/solid-objects-ruby
Commit |
 [Low impact] The PR appears safe to merge; no new actionable issues were found. SummaryAdds a maintenance guide and prepares version 1.0.3.
All four earlier, unnumbered findings are addressed: the one-use helper is gone, count examples are covered, the maintainer assertion checks the name and profile link, and the changelog accurately describes the links. Reviews (2) · Last reviewed commit: "ci: pull service images from the mirror...." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
The count pattern now finds numerals and plural forms, and a test checks the pattern against examples. The maintenance page test now checks the name and profile link of the lead maintainer. The changelog no longer says that the versioning page links to the maintenance page.
ECR Public refused the PostgreSQL, MySQL, and Redis image pulls with "toomanyrequests: Data limit exceeded", so the database jobs failed before a test ran. mirror.gcr.io serves the same Docker Hub library images. The JavaScript repository moved to it in cardmagic/solid-objects-js#79.
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
docs/maintenance.md. It tells a reader who maintains the project, how CI checks each change, how a release is published, what the reader keeps if maintenance stops, and how to become a maintainer.docs/versioning.md, and the comparison pages no longer state a count of maintainers. The comparison pages link to the new page in their maturity answer.Checks