-
Notifications
You must be signed in to change notification settings - Fork 241
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
[Bug] git aliases don't work #593
Comments
The
|
@centreboard @Jaykul How did you install azure cli? Was it using the msi or just a pip install? |
@atbagga I used the msi |
The file is https://github.com/Azure/azure-devops-cli-extension/blob/master/azure-devops/azext_devops/dev/common/git.py => line 193
Encountering this was a bit of a pain |
@qzdl , @centreboard is this happening when you are trying to use git from git bash? can you confirm if this happens from normal terminal also or just git bash.. |
I've been running from powershell/cmd prompts. |
This is related to Azure CLI MSI not packaging/handling the az bash script. It does work for me on my windows machine since az bash script is picked from the python scripts folder. One quick fix for this could be to add windows specific hack in setting git aliases as suggested above and use az.cmd instead of az. I will explore if we can fix the Azure CLI MSI packaging and fix this properly else go with the workaround. |
…alias generation to extend support to windows
@gauravsaralMs See a hacky fix in the below commit |
@qzdl Thank you for the suggested fix. We have taken the workaround for now until this gets fixed in Azure CLI. |
Fix will be available in the next release 0.9.0, scheduled to release in this week. |
Describe the bug
Trying to use git aliases results in
To Reproduce
Azure Cli Version: 2.0.64
Azure-Devops extension version: 0.8.0
Steps to reproduce the behaviour:
Expected behaviour
git pr
should have same behaviour asaz repos pr
git repo
should have same behaviour asaz repos
Additional info
Reproduced on windows in cmd and pwsh.
from .gitconfig
The text was updated successfully, but these errors were encountered: