Vscode-gitlens: When VSCode debugger is up, no more Git blame messages

[felixfong227]

• GitLens Version: 9.4.1
  
• VSCode Version: 1.30.2
• OS Version: MacOS 10.13.6

Steps to Reproduce:

1. Developing a React app
2. Open the VSCode debugger
3. Enable the debugger
4. Attach the current debugger process to one of the React's process

Screenshots:

When the debugger is off, GitLens works jsut fine 👍 🎉

But when the debugger is enabled, it dosen't show any last commit anymore 😢

[eamodio]

This is by-design to not conflict with the debugger decorations that could also appear at the end of a line. You can forcibly toggle them back on during the debug session using the GitLens: Toggle Line Blame Annotations

Is that enough? Or would you really want them on even though they could conflict with the debugger decorations?

[felixfong227]

In my personal experiences, I saw the benefit of enabling the GitLens even during a debugging session, since it provides more information about the latest commit that costing the issue at the first place.

And having an option to enable the inline git blame annotations optionally just solve the issue.

[jpike88]

During debugging is the most likely point that you'd want to be blaming lines of code in my experience, I think it should show as much as it can.

[eamodio]

I will add an option to provide the blame annotations even when debugging.

[eamodio]

This was fixed in GitLens 9.6

[github-actions[bot]]

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.