Repository navigation
Say what the gem is now, and nothing else, in the README - #180
Merged
Merged
Conversation
The install section carried two paragraphs about which minor a pin holds and what 6.0 through 6.2.0 were, which the CHANGELOG already keeps. What stays is the two lines a host types and the one sentence saying why the pin is safe, which the guidelines ask every gem's README for. The ERB linking the two files the engine serves moves under a heading of its own. The table gained the row 6.7.0 earned: `price_field` and `percentage_field`, the two controls wearing their unit inside the border. `package.json` said 6.6.0 and its lock said 6.0.0-alpha. Neither is published — the package is private — but a version in the tree that names no release is a version somebody reads and believes.
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 install section carried two paragraphs about which minor a pin holds and what 6.0 through 6.2.0 were, which the CHANGELOG already keeps. What stays is the two lines a host types and the one sentence saying why the pin is safe, which the guidelines ask every gem's README for. The ERB linking the two files the engine serves moves under a heading of its own.
The table gained the row 6.7.0 earned:
price_fieldandpercentage_field, the two controls wearing their unit inside the border.package.jsonsaid 6.6.0 and its lock said 6.0.0-alpha. Neither is published — the package is private — but a version in the tree that names no release is a version somebody reads and believes.