On 2024-07-27 at 22:38:22, Michael Salman wrote: > Thank you for filling out a Git bug report! > Please answer the following questions to help us understand your issue. > > What did you do before the bug happened? (Steps to reproduce your issue) > Using visual studio created a project and initialized it. Git works fine > under vs > What did you expect to happen? (Expected behavior) > Using a command prompt I cd to where the repository is and give the command > git status. > What happened instead? (Actual behavior) > It reports that this is not a valid repository. I noticed that the > repository does not have a .git file > What's different between what you expected and what actually happened? > Using command prompt if I cd to a different repository (which has a .git > file) the git status command works fine A Git repository with a working tree doesn't strictly have to have a `.git` file or directory, but if you don't have one, you have to explicitly set configuration options or environment variables to make this work. Since I very much doubt that was done here, it sounds like this actually is not a Git repository, and Visual Studio has a bug that causes it to either misconfigure Git or not work with it properly. It should at least provide you sufficient information to allow you to determine how it initialized the repository and where it's storing the data so you can properly work with it using the command line tools. In any event, this sounds like a Visual Studio bug and not a Git bug, so I'd report it to the appropriate Visual Studio issue tracker. I don't think there's anything we can do here, since we don't know how Visual Studio is invoking Git or how it's configuring the repository. -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
