This repository has been archived by the owner on Apr 18, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
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
b7afb30
to
813523f
Compare
Pull Request Test Coverage Report for Build 243
💛 - Coveralls |
813523f
to
b9c3774
Compare
JhChoy
reviewed
Jan 23, 2019
b9c3774
to
bb763a6
Compare
JhChoy
reviewed
Jan 23, 2019
bb763a6
to
6dd30c8
Compare
junbeomlee
approved these changes
Jan 23, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
JhChoy
reviewed
Jan 23, 2019
JhChoy
reviewed
Jan 23, 2019
ea85ddf
to
1dafe57
Compare
JhChoy
reviewed
Jan 23, 2019
JhChoy
reviewed
Jan 23, 2019
1dafe57
to
2f8637d
Compare
2f8637d
to
f2f1e82
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
config
About config files(service.vvisp.json, state.vvisp.json, .env etc)
enhancement
New feature or request
utils
About vvisp-utils
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
only supports MNEMONIC
Issue Number: #61
What is the new behavior?
now vvisp support PRIVATE_KEY instead of MNEMONIC
Does this PR introduce a breaking change?