Replies: 1 comment
-
Update: in addition to being linked to how to check out remotes via git shell, I figured out how to do it from github desktop too. Vastly easier and faster than VS2019 even when it isn't haunted. I'm still curious why it does this though, but it's not longer a major block to me fixing people's stuff. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So the last several times I've tried to juggle my remotes of other people's BN forks, I get this cursed mess in my fetch from and pull from panels:
I assumed that this was maybe some accident of having a redundant copy of someone's remote but I don't spot any in my remote manager:
Moreover, when I try to fetch someone's branches so I can check one out and fix something for them, these days I'm regularly getting the claim that there's no new changes, but don't have it available in my remotes to check out:
Last time this happened I just kept alternating between fetching from and pulling from the offending remote and it eventually just worked, but haven't repeated that success so far this time. My VS2019 is haunted as far as I can determine, unless the issue is I have vastly too many remotes in my remote manager and that causes it to just aggressively shit itself, in which case culling remotes I don't need to look at as often might presumably help, but I don't notice any lag spikes when trying to fetch these nor any error messages popping up to suggest it's timing out.
Beta Was this translation helpful? Give feedback.
All reactions