Remove extra whitespace from README.md #2
Merged
Conversation
This file contains 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
|
Thank you for running the GitHub Actions! The expected error did indeed occur: https://github.com/skryukov/typelizer/actions/runs/10521862290/job/29153381783?pr=2#step:5:12 . |
davidrunger
force-pushed
the
remove-extra-readme-whitespace
branch
2 times, most recently
from
89b54b5
to
030b88d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change removes some extra spaces from README.md.
(This is probably a tiny positive change, but my actual motivation for submitting this PR is primarily that I am seeing an error (
TypeError: no implicit conversion of nil into String) when running the specs locally, and also when running the specs in GitHub Actions on my fork (link), and I want to confirm that those errors will also occur here in this repo's GitHub Actions (and for others locally), as well, and, if so, open a discussion here about how to fix those errors.)