-
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
Broken "gitlens.blame.line.enabled" setting #242
Comments
yeah, it is true, I got this too. But very strange, it is ok now when I set it true, then false again. |
@douglarek That fix works for a while and then it seems to revert. Not sure what might be triggering the revert. |
@WoodyWoodsta yeah, you are right; so puzzled |
seems reverted in 1 min for me too |
So sorry -- will be putting out a release as soon as I get this fixed (should be soon --- just woke up) |
Thank you all for your patience -- 7.5.2 has been pushed to the marketplace and should resolve this issue. Please let me know if not. Again sorry for the inconvenience! |
microsoft/vscode#15756 can't happen soon enough. Please upvote ;) |
works like a charm from my side! Thanks for quick fix! |
If the configuration is being set for the first time ever, the problem persists (with Switching the value to (I have Mac OS 10.13.2 (17C205), VSCode: Version 1.19.3 (1.19.3)) |
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.blame.line.enabled" setting not working anymore
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: