chore: it restores inquirer for prompting external commands#1201
Merged
ematipico merged 3 commits intowebpack:nextfrom Feb 10, 2020
Merged
chore: it restores inquirer for prompting external commands#1201ematipico merged 3 commits intowebpack:nextfrom
ematipico merged 3 commits intowebpack:nextfrom
Conversation
Co-Authored-By: James George <jamesgeorge998001@gmail.com>
|
@ematipico Please review the following output log for errors: See complete report here. |
rishabh3112
reviewed
Feb 5, 2020
Member
rishabh3112
left a comment
There was a problem hiding this comment.
Should we increase timeout for init-generator test? It has been failing CI for quite some time.
Contributor
Author
|
Maybe later. For now we skipped it. |
rishabh3112
approved these changes
Feb 7, 2020
Member
|
Lets merge it when CI passes |
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.
What kind of change does this PR introduce?
Fixes #1200
Did you add tests for your changes?
Not needed
If relevant, did you update the documentation?
Not for now
Summary
A fix for the bug was already there but we have uncomment the code and make a new release
Does this PR introduce a breaking change?
No
Other information