`uv init` cannot create `.git`

[gbaian10]

Summary

When I run uv init temp --verbose, it cannot generate the .git folder and .gitignore file.
But if I explicitly specify the VCS with uv init temp --verbose --vcs git, then it does create them.

I usually run this in another environment where this issue does not occur.
Is it possible that something is causing it not to create git-related resources?

DEBUG uv 0.7.3
DEBUG No Python version file found in ancestors of working directory: /home/gbaian10/temp
DEBUG Checking for Python environment at `temp/.venv`
DEBUG Searching for default Python interpreter in managed installations or search path
DEBUG Searching for managed installations at `.local/share/uv/python`
DEBUG Found `cpython-3.10.12-linux-x86_64-gnu` at `/usr/bin/python` (first executable in the search path)
DEBUG `git rev-parse --is-inside-work-tree` failed but didn't contain `not a git repository` in stderr for `/home/gbaian10/temp`
DEBUG No Python version file found in ancestors of working directory: /home/gbaian10/temp
DEBUG Writing Python versions to `/home/gbaian10/temp/.python-version`
Initialized project `temp` at `/home/gbaian10/temp`

Platform

Ubuntu 22.04

Version

uv 0.7.3

Python version

No response

[konstin]

What does this print when run before creating the .git folder?

git rev-parse --is-inside-work-tree

[gbaian10]

What does this print when run before creating the .git folder?

git rev-parse --is-inside-work-tree

fatal: not a git repository (or any of the parent directories): .git

But when I run uv init temp --verbose --vcs git, it gets the same output verbose, but it successfully created a Git repository.

---

In another normal environment (where Git is generated correctly), I ran uv init temp --verbose and got the following output.

DEBUG uv 0.7.3
DEBUG No Python version file found in ancestors of working directory: /home/vscode/temp
DEBUG Checking for Python environment at `temp/.venv`
DEBUG Searching for default Python interpreter in managed installations or search path
DEBUG Searching for managed installations at `.local/share/uv/python`
DEBUG Found managed installation `cpython-3.13.3-linux-x86_64-gnu`
DEBUG Found `cpython-3.13.3-linux-x86_64-gnu` at `/home/vscode/.local/share/uv/python/cpython-3.13.3-linux-x86_64-gnu/bin/python3.13` (managed installations)
DEBUG Not a Git repository `/home/vscode/temp`
DEBUG No Python version file found in ancestors of working directory: /home/vscode/temp
DEBUG Writing Python versions to `/home/vscode/temp/.python-version`
Initialized project `temp` at `/home/vscode/temp`

[konstin]

The only reason why Git would fail to initialize is when git rev-parse --is-inside-work-tree fails oddly, but I can't really tell why this fails as I can't reproduce the environment in which it fails.

[gbaian10]

I reinstalling uv also had no effect and did not solve the problem.
However, if I run it again in a clean Docker environment, I can get the correct result, and I am unable to reproduce this issue in a new environment myself.
It's possible that something on my local machine is causing this problem, but I haven't been able to pinpoint the source of the issue.

[konstin]

Did you change the PATH environment variable in a way that git wouldn't work or point to a non-Git executable?

[gbaian10]

When I run the following command, I only get two system-level paths.

where git

/usr/bin/git
/bin/git

[Shadow-Xin]

The same issue also appeared on my newly purchased Mac Mini M4. I installed git and uv using Homebrew, and when I run the 'where git' command, the result is:

/opt/homebrew/bin/git
/usr/bin/git

Could it be a bug?

[konstin]

@Shadow-Xin Do both those gits work and show the same output on stdout and stderr for git rev-parse --is-inside-work-tree?

[Shadow-Xin]

I got it: Because i have installed two gits.After i run brew uninstall git,the problem solved.
@gbaian10 Maybe you should uninstall one of these gits.

[gbaian10]

I deleted /bin/git, which caused /usr/bin/git to be deleted as well. As a result, my entire system no longer had git.

I used sudo apt install --reinstall git to reinstall git, but when I run where git I still get the same two paths, and the problem where uv cannot create the .git folder still persists.

[Etyctmlrls]

It is necessary to ensure that your command line can use the git command.