There is a warning. IIRC it says "are you sure you want to discard all changes? This action is unreverisble". In the context of version management. Creating a file is a change. And just below the button to discard all changes is the list of changes. In that list he could've seen 3000 changes of the type "file creation", when you discard a file creation, it means to undo the creation, which is a deletion.
The button days what is going to do. There is a warning about what it's going to do. And there is a list of the exact changes it's going to undo.
The only way to avoid this from happening is to not have the button exist. In that case, the users that actually want to discard all changes would be unable to do so.
This user was not using git though, he was using vs code. That button doesn't say "git reset" it says "discard all changes". And btw, what it does is "git clean", which is something that git can do.
Just below the button there is a list of all the changes. In his case, there were 3000 changes of the type "file creation". Discarding a file creation can only be made one way: deleting the file.
Anyway, this user is presumably in his learning phase, I would not assume that he knows what git reset or git restore actually do.