github-markup: display basename instead of entire $0#1131
Merged
Conversation
Contributor
|
(We also have to accept the CLA. \o/) |
Contributor
|
Build errors are unrelated; fixing them up in #593. |
Contributor
Author
Hah, I was wondering about that! Travis looks unhappy for reasons unrelated to this PR. |
Contributor
Yeah, we didn't respond in time to the migration onto trusty, and we still depend on that a PPA only packaged for precise 😥 Will merge this now since it's all good. |
krzysztof293
approved these changes
May 16, 2024
|
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
3 participants
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.
The
$0in the usage text will be the full path when being executed via an rbenv shim, which leads to excessively long help text. For example, here's what the help text looks like for callinggithub-markdownwith no arguments.Before:
After: