Every once in a while, you can refresh your memory by reading the man page.
Or if, like me, you use Emacs, Magit exposes everything quite clearly.
this post was submitted on 03 Mar 2024
1097 points (97.7% liked)
Programmer Humor
19501 readers
1141 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
If you happen to forget the -m though, you may also need to have mastered exiting vim
Me as an Emacs user, who omits -m on purpose to practice quitting vi in case I really need it
you're an emacs user who has vi set up as the default editor on your system?
(You can change it altering the $EDITOR env var)
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(11 replies)
Aye, most of my 10 year career in web dev is pretty much those commands. However, some advanced git concepts are worth diving into. Stuff like git bisect that can narrow down the exact commit that broke your app is an absolute life saver. Knowing how to git cherry-pick is also a git skill professionals should be comfortable doing. Migrating work from one branch to another without merging the entire branch is pretty common.
All these comments and no one is going to point out that this is invalid?
The git stage and git commit don't have any terminator, so it's all one "command" and will fail. Then there's a single & between git commit and git push, so it would run in parallel, so it would also fail.
Also, don't git stage . people. Or at least do a git status before to make sure you didn't stage file-with-all-the-production-secrets
The comma and ampersand are plain English, not one big command
Pffft... all of my api keys are open source. Having more eyes on them will make them more secure!