Support asset arguments after tag argument in release create command #2113
+14
−3
Conversation
hnakamur
force-pushed the
hnakamur:support_asset_arguments_in_release_create_command
branch
hnakamur
force-pushed the
hnakamur:support_asset_arguments_in_release_create_command
branch
to
eb87e2f
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.
This pull request add support for optional asset
<FILE>arguments after the<TAG>argument inhub release createcommand.I think it is easier to use asset arguments than asset options because you can specify glob patterns like
*.tar.xzif the shell support expanding glob patterns.Also add a note that
-aoption can be specified multiple times in the long help ofhub release create command.