Maven (famous)@lemmy.zip to Programmer Humor@programming.dev · edit-23 months agoMicrosoft Please Fixlemmy.zipimagemessage-square106fedilinkarrow-up1560arrow-down117file-text
arrow-up1543arrow-down1imageMicrosoft Please Fixlemmy.zipMaven (famous)@lemmy.zip to Programmer Humor@programming.dev · edit-23 months agomessage-square106fedilinkfile-text
minus-squareOmega_Jimes@lemmy.calinkfedilinkarrow-up55arrow-down1·3 months agoI’m not great at English, but “discard all changes” shouldn’t ever mean “Delete”.
minus-squareMichal@programming.devlinkfedilinkarrow-up26arrow-down4·3 months agoIn the context of version control it does. Discarding a change that creates a file means deleting the file.
minus-squareOmega_Jimes@lemmy.calinkfedilinkarrow-up4arrow-down1·3 months agoOk fair enough, but I’m under the impression these files existed before the source control was implemented. I guess it’s all up to how the program handles existing files.
minus-squareFiskFisk33@startrek.websitelinkfedilinkarrow-up4·3 months agoI guess the newly created git repository was empty, and all the files that was present in the folder represented “changes”
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up3·3 months ago“Discard” is not a git operation.
I’m not great at English, but “discard all changes” shouldn’t ever mean “Delete”.
In the context of version control it does. Discarding a change that creates a file means deleting the file.
Ok fair enough, but I’m under the impression these files existed before the source control was implemented.
I guess it’s all up to how the program handles existing files.
I guess the newly created git repository was empty, and all the files that was present in the folder represented “changes”
“Discard” is not a git operation.