In case anyone else is wondering, or simply doesn't like reading screen shots of text, this is apparently a real report:
this post was submitted on 20 Nov 2024
863 points (97.5% liked)
Programmer Humor
19623 readers
1229 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Steps to Reproduce:
1.Go near this fucking shit editor.
2.Commit the deadly sin of touching the source control options.
🤣
- Ignore the scary warning VS Code shows you when you press the button.
I dunno, “discard changes” is usually not the same as “delete all files”
load more comments
(14 replies)
load more comments
(11 replies)
load more comments
(1 replies)
load more comments
(1 replies)
I agree with the "learn the CLI", but to newcomers I'll also suggest to look at the IDE/editor's output channel - if there's GUI for Git, there are also most likely logs for what's happening under the hood - even if a little noisy, it can be a good learning resource. And of course if you're learning and unsure of what's happening (with the CLI or through a GUI), do so in a non-destructive manner (by having proper backups).
If the files were already staged then git should have blobs in the git folder, so they should be recoverable.
load more comments
(7 replies)
VSCodium better
If you ever happen to have 5000 uncommitted files, you shouldn't be asking yourself if you should commit more often. You should be asking yourself how many new repos you should be making.
load more comments
(8 replies)