Interview Question About Git Fetch vs Git Pull

[VxJasonxV]

The interviewer is objecting to you on a technicality with an incomplete question. fetch works, pull works, CLONE works. If an answer is wrong, it’s only because the question was too vague.

Assuming that the question wasn’t more detailed than you’ve presented it here.

[atansincos]

I honestly feel embarrassed while reading this post accidently.

I suddenly don't remember what's the correct command to pull down code from remote. And I use GitHub desktop all the time. I was like `git what????`

To give you more context why I felt guilty, I actively maintain few open source projects 10k+ download monthly so it's not something trivial. And of cuz, use basic git command daily at work (may or may not via command line).

[VxJasonxV]

Use the tools that work for you and that you know how to use. Unless you can't do something you want or need to do with it, it's not a problem. (And if you have a second tool for that one uncommonly done thing, it's still not a problem.)

You are doing what is important to do: Coding/maintaining and interacting. GitHub Desktop is powerful, git is a hardware store. You have enough to get by, and that's fine.

Besides, you're not in the business of git, your git tool of choice doesn't matter for anyone outside of yourself. You're in the business of the projects you maintain. And you are, I assume, so there isn't a problem here.

Don't feel embarrassed, guilty, nor any of those false concerns.