VersionControl
Post #7302 · source on Telegram
Never Be Afraid to Make a Mistake Unless It's in Git
Description
A tweet-style meme from the account 'Dev meme @devs_memes' (with a blue verified checkmark) on a black background. The text reads: 'Never be afraid to make a mistake Unless, it's in Git Then be afraid Be very afraid'. The profile picture shows a sketched face with sunglasses. The humor plays on the permanence of Git history where mistakes are forever preserved in commit logs, force pushes to main are catastrophic, and rebasing gone wrong can ruin everyone's day
More like this
More like this in VersionControl →
Use J and K for navigation
Comments
15Comment deleted
Git never forgets, and neither will your coworkers when they run git blame on that one commit from 3 years ago
There are only two certainties in a developer's life: death, and that moment of cold-sweat panic after you type 'git push --force' and before you hit Enter
Git never forgets - unless you rewrite history, and then the entire team never forgives
After 15 years in the industry, I've learned that the only thing more permanent than a production database is a mistaken force push to main that overwrote three sprints of work - at least the database has backups and a DBA who answers their phone
Git: where 'git push --force' is the technical equivalent of 'hold my beer' - except the beer is your entire commit history and everyone's watching
Reflog is a parachute - until you --force origin/main and the recovery plan becomes 'find the one teammate whose clone hasn’t pulled yet.'
Architects fear monoliths; seniors fear 'git reset --hard HEAD~1' on a shared main
Pushed .env - "Oops"😁 Comment deleted
ohshitgit.com Comment deleted
knowing how to use git cmd is important for automation, but when someone doing everyday stuff and fucking up in ways like these - most fundamental problem is that they are lacking an overview, should've used a visual git wrapper to see how each change actually affects the commit graph Comment deleted
Can confirm that I have been in most of these situations and have applied most of the listed solutions. Not sure what that means, but ohshitgit for sure. Comment deleted
13bb98a: remove hardcoded credentials in src/www/mission-control/nuke-activation.php Comment deleted
There is nothing that git reflog couldn't fix Comment deleted
Fortunately we already have Jujutsu git client, that has "jj undo" to just undo anything you made wrong in VCS Comment deleted
https://github.com/sourcegit-scm/sourcegit Comment deleted