Reading your comment and #32459, I realize that VSCode source control did have some major issues back then.

It looks like they have improved though, as the latest VSCode I use doesn’t auto-initialize repositories anymore.

It’s not that. It means discard all changes made after the last change committed to this local repository.

He wouldn’t have seen the “Discard Changes” button at all if source control wasn’t already setup (and detected by VSCode).

No program will delete files either when you initialize source control.

“Changes” encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.

If the change is an edit to a tracked file, “Discard Changes” will reverse the edit. If the change is a new untracked file, “Discard Changes” will remove it as intended.

It can also be both at the same time, which is why VSCode uses “Changes” instead of “Files”.

Look at what they need to mimic a fraction of my cuteness.

What, your printer doesn’t have a full keyboard under its battery? You’ve gotta get with the times my man.