-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide some kind of welcome/orientation for first-time users #51
Comments
👍 |
@RogerThiede FYI in the next GitLens version (coming soon) there will no longer be a restriction on having to open a folder for GitLens to work. |
@RogerThiede I've just published v3.2.0 which adds support for working without a loaded folder -- hope that helps! |
Awesome! It now works intuitively for me when opening files.
|
I just started with visual studio code, and tried gitlens, I am getting the Error that it cant find my git installation so as suggested I wanted to change the gitlens.advanced.git. But nowhere is actually explained where you enter those commands because they didnt work in cmd + shift + p, or in the terminal so I am kinda confused. When I open cmd + shift + p and enter gitlens I get some commands listed but no way to change the gitlens.advanced.git.... |
@Giusti sorry for the delayed response, I didn't notice the update to this issue (FYI in the future its best to open a new issue unless there is a true duplicate) the So you would add a line that looks something like Hope that helps. |
fix cannot open file gitkraken#51
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
GitLens has a bunch of features many of which are not very discoverable. Figure out ways to welcome/orient users and/or make features more discoverable.
Any ideas are very welcome here.
The text was updated successfully, but these errors were encountered: