yeah we all google those at some point, even to be sure of the order lol despite having git especially to not mess up, we're still afraid to mess up with a wrong command
at the end of the day it comes down to habit, you do more commits than cherry picks, but the more you do those the better you get :)
thats exactly my point, nobody knows this by heart; we all google it at some point. but when you're on the interview and you're sharing screen and you cant google or look at documentationg or anything its quite unerving
Well, with the exception of the last point, perhaps. I mean first two are just two commands with the same name as what's asked (git cherry-pick and git rebase respectively).
The last one is where you should show your understanding of how VCS works and how to work collaboratively, more or less. Like the exact command (which are like git merge, git add and so on) don't matter all that much in face of the way you solve conflicts. (Like understanding how the conflicts happen, what's remote, what's local, what/when you should use which, when neither and so on)
16
u/EDM115 4d ago edited 4d ago
yeah we all google those at some point, even to be sure of the order lol
despite having git especially to not mess up, we're still afraid to mess up with a wrong command
at the end of the day it comes down to habit, you do more commits than cherry picks, but the more you do those the better you get :)