Update README with new logo, change Congfig.LOGO, run linter #1443
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
Codecov Report
@@ Coverage Diff @@
## master #1443 +/- ##
==========================================
+ Coverage 91.32% 91.32% +<.01%
==========================================
Files 17 17
Lines 1717 1718 +1
Branches 322 322
==========================================
+ Hits 1568 1569 +1
Misses 123 123
Partials 26 26
Continue to review full report at Codecov.
|
Add new logo and update contents of README. Update README.rst Fix image syntax. Update README.rst Fix README links.
This was referenced Dec 30, 2018
Closed
Update logo text Reformat app.py
ahopkins
changed the title
ahopkins
changed the title
yunstanford
approved these changes
Dec 30, 2018
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.
The main purpose of this was to add the new logo and update contents of README.
However, it also addressed the issue with #1432 and #1441. In running the test suite, it became apparent that there was some formatting changes needed from
blackandisort.