Closed jb-jonBoone closed 4 weeks ago
Can you please add more detail as to the issue you are experiencing and/or the steps to reproduce it? How are you opening the repository -- locally, shared drive, remote extension, etc?
Also, if this issue is reproducible, can you please enable debug logging by running from GitLens: Enable Debug Logging from the Command Palette (F1 or ctrl/cmd+shift+p). This will enable logging to the GitLens and GitLens (Git) channel in the Output pane.
Once enabled, please reproduce the issue, and attach the log from the both GitLens and GitLens (Git) channels.
Thank you!
This issue needs more information and has not had recent activity. Please provide the missing information or it will be closed in 7 days. Thanks!
Closing this issue because it needs more information and has not had recent activity. Please re-open this issue if more details can be provided. Thanks!
Description
In this environment: MacBook Pro w/Apple M3 Pro, 18 GB RAM
I opened a Node.js project under git source control.
GitLens Version
15.2.0
VS Code Version
Version: 1.91.1 (Universal) Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729 Date: 2024-07-09T22:07:54.982Z Electron: 29.4.0 ElectronBuildId: 9728852 Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-electron.0 OS: Darwin arm64 23.5.0
Git Version
git version 2.45.2
Logs, Screenshots, Screen Captures, etc
The extension is unable to recognize that I already have opened a folder containing a git repository, so the extension suggests that I open an issue.