Closed jmevel closed 9 months ago
So... I'm actually closing this ticket.
I thought multiple remotes was the root cause but it actually seems not. I still don't understand what is causing the issue on my repository then. It's working well on any other project I'm working on (all of them have a single origin
remote).
But I tried to do the Steps To Reproduce
and it's working...
EDIT: and now all of a sudden it works on the repository I had this issue. I did NOT modify any file, 1 minute ago it still wasn't working 🤔
May be related to #715
Describe the Bug
When working on repositories with multiple remotes both
Git: View File History
andGit: View Line History
commands do nothing. This is an issue on forks when one would want to keep their version up-to-date with the repository the fork will eventually be merged into. In that case we add a second remote and we rebase the latest history onto the branch of our fork we are working on.Steps To Reproduce
git remote add upstream https://github.com/original-repo/goes-here.git
Output
(Ctrl + Shift + U
) and selectGit History
in the dropdownCtrl + Shift + P
)Git: View File History
or theGit: View Line History
commandExpected Behavior
Line History
or theFile History
windowgit log -L11,11:my-file.yaml --full-history --pretty=oneline --date-order --decorate=full --skip=0 --max-count=10 (completed in 0.365s)
is shown in theOutput
windowActual Behavior
Line History
norFile History
window appearsOutput
windowEnvironment