4 ms·
Honestly, a lot of what's wrong in git is that people seem to mostly memorize or copy-paste a finite amount of commands, and when something goes wrong they are
by mFixman 9y ago
Honestly, a lot of what's wrong in git is that people seem to mostly memorize or copy-paste a finite amount of commands, and when something goes wrong they are completely lost unless they can find a way to copy-paste a solution.
Instead of saving a 6 command list for some use cases, why not just get used to the simple but kinda unintuitive way of how revisions and branches work? If you know that, you can solve any problem with `commit`, `checkout`, `reset`, `reflog`, and occasionally `cherry-pick`.
- ufo 9y agoI think you already answered your own question. It is very hard to get comfortable with things if they are unintuitive :)
- CJefferson 9y agoQuick quiz, what does 'git checkout x/y' do? I am aware of users hitting at least 3 interpretations.
- Nimitz14 9y agoI'd say it changes your code to match that of a branch in your local copy of the repo.
- CJefferson 9y agoIt resets the file x/y, or checks out branch y of remote x, or checks out local branch x/y. I've had confused users manage to create al of these cases, and git is very unhelpful in explaining the difference between the three cases.