Oof, thanks for that warning. So it will blow away changes you haven’t merged (only fetched)?
I guess git can’t tell the he difference between “not merged yet” and “don’t want to merge, please destroy”
I guess git can’t tell the he difference between “not merged yet” and “don’t want to merge, please destroy”
However, we use vscode, and I rather like auto fetch. But apparently this workflow would destroy something auto fetched that I might not have even noticed.