Open axosoft-ramint opened 10 months ago
I have the same issue since... EVER it seems that it does some kind of mixup between the true commit/diff and the last committed PR
Note that I have this issue on EVERY line
However it seems to work properly when a commit didn't come from a PR, unsure if that's related
i have the same question and how do you solve this problem ,like using other pluging?@Bibendus83
Description
Case 1:
How is this autolink generated? It's pointing at an unrelated remote, instead of the PR target (which is also origin) so I get a 404. I would expect it to either pick the correct PR target (fork) or default to origin - or, if someone made an oopsie, then perhaps even the fork that the PR is coming from. But it's picked a seemingly-random one.
Case 2:
I’ve been experiencing something similar here, where the commit looks correct but the associated PR is one of my recent PRs instead of the PR where the commit was introduced.
GitLens Version
14.6.0
VS Code Version
No response
Git Version
No response
Logs, Screenshots, Screen Captures, etc
No response