-
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
Blame annotations not showing anymore after update #1882
Comments
Hello, I have the same issue :(
|
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! |
I think it's related to symlinks. When I open my project through a path that contains a symlink (created via To reproduce create a link like this via Command Prompt:
|
Same here. Instead of sending canned responses on marketplace reviews about asking to open issues on github*, how about getting your house in order first? *only here to annoy your developers -by contributing absolutely nothing with this reply- because your management team obviously pushed for a sped up release, and because your management -and probably an intern seo- thinks you can damage control by redirecting your user base to github issues. you mad yet? good, get mad at your management, show them this ("this" being utter incompetence on gitkraken's takeover) p.s. maybe i'm wrong about most of this, but i'm definitely not wrong about the clear demonstration of utter incompetence |
I confirm the problem - #1926
|
For users facing this issue, if you happen to have configured git-blame-ignore-revs, this might be relevant: #1143 |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
Can you please verify this fix in the GitLens insiders edition? You can install the GitLens insiders edition from here. Please be sure to disable or uninstall the stable version of GitLens first. |
still have such issue with gitlen 2022.4.2705
|
Going to check. |
…ymbolic link, quick and dirty prototype, not to be merged as is
I just installed the Insider version and disabled the regular extension version, and restarted VSCode, and I notice no changes. I can see blame on the lines when viewing the original file (
macOS 12.4 (m1) |
Really sorry for the delay on this -- the major refactor GitLens underwent in version 12 to bring virtual repository support and web support made tracking down a performant solution much harder than I had expected/hoped. Can you please verify this fix in today's GitLens insiders edition? You can install the GitLens insiders edition from here. Please be sure to disable or uninstall the stable version of GitLens first. |
I have verified blame annotations work again for folders containing symlinks. |
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 used to show the last commit for each line of code before the update. Now it's not showing anything. The "Current Line" option is turned on.
Additionally, the Toggle Line Blame command is also not working for me.
git --version
2.28.0.windows.1code --version
1.64.2The text was updated successfully, but these errors were encountered: