Maven (famous)@lemmy.zip to Programmer Humor@programming.dev · edit-26 months agoMicrosoft Please Fixlemmy.zipimagemessage-square334fedilinkarrow-up1880arrow-down123file-text
arrow-up1857arrow-down1imageMicrosoft Please Fixlemmy.zipMaven (famous)@lemmy.zip to Programmer Humor@programming.dev · edit-26 months agomessage-square334fedilinkfile-text
minus-squarecocobean@bookwormstory.sociallinkfedilinkEnglisharrow-up43·6 months agoAlso, why not send them to the recycle bin? I never really thought about it before, but that does seem a reasonable UX improvement for this case
minus-squaremurtaza64@programming.devlinkfedilinkarrow-up4·6 months agoI wonder if there’s already a git extension to automatically stash the working tree on every clean/reset/checkout operation…
minus-squarestetech@lemmy.worldlinkfedilinkarrow-up4arrow-down1·6 months agoBecause “the underlying Git nukes them right away, so why shouldn’t we perma-delete the files, too?” Anything else’d be effort…
minus-squareNate@programming.devlinkfedilinkEnglisharrow-up9·6 months agoHonestly it probably just runs the underlying git command
minus-squarestetech@lemmy.worldlinkfedilinkarrow-up1·6 months agoSorta, but sorta no. It was actually addressed in https://github.com/microsoft/vscode/issues/32459 – the GUI implied a different git command than what actually got executed!
Also, why not send them to the recycle bin? I never really thought about it before, but that does seem a reasonable UX improvement for this case
I wonder if there’s already a git extension to automatically stash the working tree on every clean/reset/checkout operation…
Because “the underlying Git nukes them right away, so why shouldn’t we perma-delete the files, too?”
Anything else’d be effort…
Honestly it probably just runs the underlying git command
Sorta, but sorta no.
It was actually addressed in https://github.com/microsoft/vscode/issues/32459 – the GUI implied a different git command than what actually got executed!