The GitHub repo: https://github.com/ndp/git-cheatsheet
Visual Git Cheat Sheet
11–20 of 43 posts
Re: Visual Git Cheat Sheet
#12I love this cheat sheet and yes, it's not obvious that you need to click the boxes to see all commands emanating, or arriving, into that box. The GitHub repo: https://github.com/ndp/git-cheatsheet
Re: Visual Git Cheat Sheet
#13like workspace vs. local repo. that IS NOT explained, but all kinds of stuff about stashes is present.
people that know git very well have no clue how to teach git to others. none.
Re: Visual Git Cheat Sheet
#14All this information is already natively available in the help menus, and new people should probably generally stick to things like egit if they're completely lost and need a beginning grasp imo.
Re: Visual Git Cheat Sheet
#15I'm an expert in git, but at a glance I don't see what you're trying to do here. It's like dumping an alphabetical list of methods on someone. An expert already knows them, and it's a weird way to present it to someone new to coding. All this information is already natively available in the help menus, and new people should probably generally stick to things like egit if they're completely lost and need a beginning g…
Click a box and you get all that's coming, and all that's going, to that box.
Hover over a command and the display area at the bottom of the screen explains the command.
If you're looking at this on mobile, and puzzling why this might be a great thing, this predates your device's tech by a very long time.
Re: Visual Git Cheat Sheet
#16Felt like it complicated things rather than clarified. For a newcomer to git I imagine it could be overwhelming.
Re: Visual Git Cheat Sheet
#17Re: Visual Git Cheat Sheet
#18Is it because the complexity is really needed, or if papering over them and making it user friendly has failed? For example, you won't find a cheat sheet of SQL commands submitted and upvoted so many times on HN, even though SQL implementation and internals are very complicated. Reason being it's able to hide the implementation details and abstract it away.
At the very least the terminology in git is very confusing. Especially 'checkout' for people who came from a SVN/CVS background.
Re: Visual Git Cheat Sheet
#19Re: Visual Git Cheat Sheet
#20Why is git the hardest to grok for most developers compared to almost anything else in the web dev ecosystem? It always feels like a tool with very less or very leaky abstractions. Is it because the complexity is really needed, or if papering over them and making it user friendly has failed? For example, you won't find a cheat sheet of SQL commands submitted and upvoted so many times on HN, even though SQL implementa…
I've been through 3 source control systems now, and Git is by far the easiest. I only branch, clone/init/add/commit/push/pull and merge. (And now most through the gui in vscode) There are some minor fixes I've had to look up, but it's rare.
Almost all the complaints I hear about are from very obscure commands and situations I've never seen.
Is using Git in a simple way the answer to everyone's problems with it?