Joey Kelroy
Joey Kelroy
Hello @tomika and others, this looks similar to #2144. [As I mentioned there](https://github.com/gitkraken/vscode-gitlens/issues/2144#issuecomment-1609645710), I am no longer seeing this error in GitLens 14+. Can you please try updating and let...
Hello @steven-varga, I worked with you over email but would like to provide context here and close out this issue as well. To reiterate, we confirmed you were able to...
Hello @Malix-off, thanks for reporting this. For now, you can log in by downgrading to version 14.6.1 from Extensions > GitLens Settings > Install Another Version... ![Screenshot 2024-02-22 at 11...
@Malix-off this is the only open issue for this. It affects version 14.7-14.8.2. One other workaround is that in the current version, the code (`code=`) can be copied from the...
@Malix-off this has now been addressed in the pre-release. Can you check if this is now working as expected for you? You can switch to the pre-release edition of GitLens,...
@GottZ I see your email as well. It looks like your subscription is in an unexpected state and I am having the team take a look into it now.
@GottZ I sent a follow up over email - the issue with your subscription was fixed and you should be seeing Pro in GitLens now. If not, try [signing into...
@mgasparel can you please see if this issue is still reproducible in the pre-release edition of GitLens? You can switch to the pre-release edition of GitLens, by clicking on the...
Hello @jskccom, testing a few difftools (Beyond Compare and Winmerge), I am not having an issue using GitLens to `open changes (difftool)` when there is a space in the path....
My Repro Steps on macOS (13.2.1): - switch commit graph to panel layout - close the panel - close VS Code - Select Open with GitKraken on the clone menu...