Repository navigation
Fix indent on README - #89
Merged
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #89 +/- ##
=======================================
Coverage 95.76% 95.76%
=======================================
Files 9 9
Lines 543 543
=======================================
Hits 520 520
Misses 16 16
Partials 7 7 Continue to review full report at Codecov.
|
Owner
|
Thanks, but could you also fix that on another README? |
Contributor
Author
@panjf2000 |
Owner
|
Thanks~ |
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
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.
name: Pull request
about: Propose changes to the code
title: 'Fix indent'
labels: ''
assignees: ''
1. Are you opening this pull request for bug-fixs, optimizations or new feature?
No.
2. Please describe how these code changes achieve your intention.
There are wrong idents on README.md.
3. Please link to the relevant issues (if any).
4. Which documentation changes (if any) need to be made/updated because of this PR?
4. Checklist