Better --prompt Handling #549
Open
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
Signed-off-by: Daniel J. Perry <dperry45@gatech.edu>
Signed-off-by: Daniel J. Perry <dperry45@gatech.edu>
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.
I always use the
--promptoption to ensure that the correct release is choosen, but the process of choosing one is a bit ambiguous. My first guess was to enter the index number of the displayed release that I wanted (1 for the first one, 2 for the second one and so on) but that was incorrect. I had to look through the source to see how to do it.So I added a little message for the user to make things more clear. I also made the input case-insensitive so that
25EA4will match with25ea4.