So do you guys pronounce it git or jit
this post was submitted on 03 Mar 2024
1097 points (97.7% liked)
Programmer Humor
19501 readers
1249 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
I once had HR ask if I was familiar with G-I-T ( she spelled it out), for a moment, my only thought was "wtf is G-I-T".
One of my first interviews in Canada I was asked what a “zed-index” is and was like what? A what now?
load more comments
(3 replies)
load more comments
(2 replies)
As someone who knows that they know very little about git, this thread makes me think I'm not alone.
I think advanced git knowledge, like RegEx, is the exception, while the norm is to know the tiny handful of day to day useful bits
How is regex git knowledge? I guess you can use regular expressions with git grep but it's certainly not a git-oriented concept...
I don't even know how to respond to this considering it has nothing to do with what I said...
load more comments
(5 replies)
what. that's not what they said. they are comparing git knowledge to regex knowledge.
Gut clone
cat ~/.bash_history | grep "gut add" | wc -l
I've typed that more times than I thought...
alias gut=git
echo alias gut=git >> ~/.bashrc
git commit -am
You don't just git to edit past commit
git blame is another good one
Yes, I think we all like to blame git
Learn to use git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.
With automated CI, I've had very few times where bisect is useful. Either the bug was introduced 1-2 commits ago, or it's always been there and the exact commit is irrelevant to the solution, since you just fix it forward.
How about git commit-tree [Hash] -p branch1 -p branch2 … -m "Dummy Message"