- [ ✓ ] I was not able to find an open or closed issue matching what I'm seeing
Setup
- Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
Initially, 2.14.2.2-64bit.
I then tested this with the portable versions below, and all had the same issue.
2.13.1-64bit
2.13.1.2-64bit
2.13.2-64bit
2.13.3-64bit
2.14.0-64bit
2.14.0.2-64bit
2.14.1-64bit
I finally found that 2.13.0.1-64bit was the most recent Git-for-Windows release that behaved as expected (it gave the status of the git repository).
$ git --version --build-options
git version 2.14.2.windows.2
built from commit: 34c1a976dcdaa107499f5c0c1c416bcfee477f94
sizeof-long: 4
machine: x86_64
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver
Microsoft Windows [Version 6.1.7601]
- What options did you set as part of the installation? Or did you choose the
defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
Path Option: Cmd
SSH Option: OpenSSH
CURL Option: OpenSSL
CRLF Option: LFOnly
Bash Terminal Option: ConHost
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled
- Any other interesting things about your environment that might be related
to the issue you're seeing?
The filesystem working directory at which the issue occurs is at the root of a Windows share. Changing the filesystem working directory ("cd"-ing) into a subfolder of this directory and then running the same git.exe command succeeded as expected.
Example:
- repository top level folder (which is the root of a Windows share):
\\server\scripts\
- command that results in varied behavior:
git.exe status
- command fails when filesystem working directory in the PowerShell session is:
\\server\scripts\
- command succeeds when filesystem working directory in the PowerShell session is:
\\server\scripts\mysubfolder\
Put another way:
cd \\server\sharename
git.exe status
- succeeds from a subfolder of the given repository:
cd \\server\sharename\mysubfolder
git.exe status
Details
- Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
PowerShell
cd \\server\sharename
git.exe status
- What did you expect to occur after running these commands?
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
...and so on...
- What actually happened instead?
fatal: Not a git repository (or any of the parent directories): .git
-
other info: the expected behavior of getting the status of a git repository which resides at the root of a Windows share succeeds with git version 2.13.0.1 (a.k.a. git version 2.13.0.windows.1, built from commit: eba7af3dbb4c846c6303c5f64102acee696c9ab0)
-
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
** insert URL here **
Setup
Initially, 2.14.2.2-64bit.
I then tested this with the portable versions below, and all had the same issue.
2.13.1-64bit
2.13.1.2-64bit
2.13.2-64bit
2.13.3-64bit
2.14.0-64bit
2.14.0.2-64bit
2.14.1-64bit
I finally found that 2.13.0.1-64bit was the most recent Git-for-Windows release that behaved as expected (it gave the status of the git repository).
defaults?
to the issue you're seeing?
The filesystem working directory at which the issue occurs is at the root of a Windows share. Changing the filesystem working directory ("cd"-ing) into a subfolder of this directory and then running the same git.exe command succeeded as expected.
Example:
\\server\scripts\git.exe status\\server\scripts\\\server\scripts\mysubfolder\Put another way:
cd \\server\sharename git.exe statuscd \\server\sharename\mysubfolder git.exe statusDetails
PowerShell
Minimal, Complete, and Verifiable example
this will help us understand the issue.
other info: the expected behavior of getting the status of a git repository which resides at the root of a Windows share succeeds with git version
2.13.0.1(a.k.a.git version 2.13.0.windows.1, built from commit:eba7af3dbb4c846c6303c5f64102acee696c9ab0)If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
** insert URL here **