3 ms·
This guide would benefit from some visuals. That is, what is happening, and why. Else, for beginners, just listing commands is too abstract. It would also help
by chiefalchemist 3y ago
This guide would benefit from some visuals. That is, what is happening, and why. Else, for beginners, just listing commands is too abstract. It would also help to elaborate a bit on why, or at least walk though a merge conflict, 'cause ultimately, that's what beginners need to be aware of. That is, Dev A made changes a file and Dev B also made changes to that file. Boom! But this is why we use Git.
- nerdponx 3y agoThe Git book, Pro Git, does a decent job of this. Also https://learngitbranching.js.org/ https://learngitbranching.js.org/
- chiefalchemist 3y agoI believe that on GitHub there are also visual examples. For me, ultimately, Git is best understood when there are visuals. The command line is cool, but if there's a tool that begs for a UI it's Git. Yeah, I know there are Git UI tools, so many the article should have suggested some of those as well?
- nerdponx 3y agoI have yet to find a Git GUI that really feels right. Recommendations?
- chiefalchemist 3y agoI've been using GitKraken which is paid (@ a fair $60 p/y). But I also see FOSS options mentioned on HN from time to time and intend to explore one of those. Perhaps I'll do an Ask HN later today?