Allow jobs keys to default to listing all keys
#252
Merged
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
This can help debug Windows installations, where the Windows CLI interacts poorly with `bundle exec jobs keys '*'`: ERROR: "jobs keys" was called with arguments [ (every file in the working directory ) ]
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 was having an issue on my Windows installation where I couldn't list any jobs through the command line.
This commit allows the "keys" command to take a default of "*", which helps Windows installations, where the Windows CLI interacts poorly with
bundle exec jobs keys '*':It's still possible to run
bundle exec jobs keys <pattern>as necessary.