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
Do not overwrite users environment variables #115455
Conversation
The current code prevents accidental usage of that environment variable and breaking auth. So I'd rather we put this behind a configuration setting, given it's such a niche scenario. I would also only move the |
@joaomoreno I have adjusted my changes accordingly. |
@eamodio What is the status of the merge? Is there anything I can do to speed up the process? |
Can we have this merged? It's incredibly frustrating |
@MCterra10 thanks for spotting the typo. I have rebased my changes onto the new mainline so it can be merged easily. @lszomoru any chance this can be merged? |
@Backfighter conflicts? |
The GIT_ASKPASS variable is currently enforced by vscode and there is no way to overwrite it. This commit adds an options to disable the integrated askpass and use your own. Fixes microsoft#111839
are the maintainers always this slow for such simple changes? |
Apologies for the delay on getting this in. This should be in tomorrow's Insiders release and the next Stable release. |
sweeeeet |
These environment variables are currently enforced by vscode and there is no way to overwrite them. Turning this arround allows the user to use a custom GIT_ASKPASS inside vscode (e.g. /usr/bin/ksshaskpass for kde wallet).
This PR fixes #111839