Path conversion in git bash #702
Labels
Comments
|
Double the slash on the path to escape msys path conversion: |
|
Please use the bug tracker only for bugs, not for questions. See https://git-scm.com/community for resources how to obtain help with using Git for Windows. |
This comment was marked as abuse.
This comment was marked as abuse.
dscho
added a commit
to dscho/git
that referenced
this issue
Oct 28, 2024
Instead of storing the Personal Access Token in an environment secret, store it in Azure KeyVault instead. This allows for much better auditing when (and where) the secret is used. Ideally, we would even switch away from using a Personal Access Token in the first place. But there is no alternative, such as a Managed Identity on GitHub, where one could define in a fine-grained way which usage scenario can be performed using that identity, and recent reorgs at GitHub suggest that adding such an alternative may not be on the list of priorities at all. So let's just stay with a Personal Access Token, but do safeguard it better by putting it into a KeyVault that can only be accessed by a narrowly-scoped GitHub Actions environment.
dscho
added a commit
to dscho/git
that referenced
this issue
Dec 10, 2024
) This is a companion to git-for-windows#702: Instead of storing the token used for the Homebrew release workflow, let's retrieve it from the Key Vault that already is used to store such information.
mjcheetham
pushed a commit
to mjcheetham/git
that referenced
this issue
Jan 20, 2025
Instead of storing the Personal Access Token in an environment secret, store it in Azure KeyVault instead. This allows for much better auditing when (and where) the secret is used. Ideally, we would even switch away from using a Personal Access Token in the first place. But there is no alternative, such as a Managed Identity on GitHub, where one could define in a fine-grained way which usage scenario can be performed using that identity, and recent reorgs at GitHub suggest that adding such an alternative may not be on the list of priorities at all. So let's just stay with a Personal Access Token, but do safeguard it better by putting it into a KeyVault that can only be accessed by a narrowly-scoped GitHub Actions environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running git version 2.7.4. I run the following command:
For some reason, the terminal/shell is converting "/data/settings" to "C:/Git/data/settings". I have git installed at "C:/Git".
I understand in most cases, this conversion makes sense. However in this context, "/data/settings" is a path on a REMOTE device, not the current filesystem. Is there a way to tell it not to convert the path?
The text was updated successfully, but these errors were encountered: