fix inconsistent indentation in README #111
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
It was a mix of tabs and spaces, and the tabs were obviously meant to be interpreted as being 4 columns wide, which is a much less common interpretation than 8 columns. So make the file self-consistent and unambiguous by replacing each tab with 4 spaces. Then fix a couple of issues with indentation in the example docker-compose file.
shawncarr
reviewed
Jun 8, 2019
Accept some fixes from @shawncarr. Co-Authored-By: Shawn Carr <[email protected]>
|
Please could this be merged soon? We are already seeing duplicate efforts crop up, e.g. #113. Thanks! |
|
thanks @aspiers I always dedicate my Friday morning to this project ;) |
|
Thanks a lot @luizeof! |
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.
It was a mix of tabs and spaces, and the tabs were obviously meant to be interpreted as being 4 columns wide, which is a much less common interpretation than 8 columns. So make the file self-consistent and unambiguous by replacing each tab with 4 spaces.
Then fix a couple of issues with indentation in the example
docker-composefile.