Update the link of swagger file and release notes in opensds README file #1191
Conversation
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
PravinRanjan10 changed the title 
Codecov Report
@@ Coverage Diff @@ ## development #1191 +/- ## ============================================ Coverage 34.82% 34.82% ============================================ Files 97 97 Lines 17622 17622 ============================================ Hits 6137 6137 Misses 10614 10614 Partials 871 871 |
kumarashit reviewed Jan 22, 2020
Collaborator
kumarashit left a comment
kumarashit left a comment There was a problem hiding this comment.
Should it be updated to v0.10.1?
added 16 commits January 27, 2020 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
What this PR does / why we need it:
Currently our opensds readme file has old link of swagger file and release notes. WHich need to be updated otherwise it shows old API's.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: