-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands called via alias do not expose that fact. #568
Comments
This should be resolved by PR #567 |
This issue is being marked as stale due to a long period of inactivity |
Nope, @github-actions. |
@frederikhors I can confirm this now works thanks to #567. I've actually made use of it here Line 102 in 8c638d3
|
Resolved via the mentioned PR; closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a command a) has defined aliases and it is b) invoked through one of those aliases, there is no way to determine whether the command was called by its primary name or one of the aliases.
The text was updated successfully, but these errors were encountered: