Post 9upxVTDAggaH15Cro0 by fritogotlayed@fosstodon.org
(DIR) More posts by fritogotlayed@fosstodon.org
(DIR) Post #9uphw5x3g15dQgLMVk by kev@fosstodon.org
2020-05-08T09:52:31Z
0 likes, 0 repeats
Ok. New day and I’m less angry. Let’s give this Git shizzle another shot.I have a Pluralsight subscription through work, so let’s do it properly - take the time, learn the tool (via CLI) and go from there.But first I need coffee, breakfast and to walk the dog (in that order). Oh, I also need to pacify the wife and do “my jobs”.Come on, Kev. You’re a semi-clever guy, you can bloody learn Git!
(DIR) Post #9upi4CytQOQnY24Qhk by WhoNeedszZz@fosstodon.org
2020-05-08T09:53:56Z
0 likes, 0 repeats
@kev I'm around right now and happy to help you out.
(DIR) Post #9upigoQycjm4i6c9D6 by tobtobxx@fosstodon.org
2020-05-08T10:00:54Z
0 likes, 0 repeats
@kev If I can recommend you a guide/book:Git Pro by Scott Chacon & Ben StraubAvailible for free on https://git-scm.com/book/en/v2.I have a physical edition and it really helped me understand the underlying concepts of git.
(DIR) Post #9upimztwtxWO0s7C2i by salvari@fosstodon.org
2020-05-08T10:00:56Z
0 likes, 0 repeats
@kev pluralsigth git courses from Paolo Perrota are really good (imho). "How git works" and "Mastering git"
(DIR) Post #9upj5vsS5TtV2CRZhY by dwagenk@fosstodon.org
2020-05-08T10:05:23Z
0 likes, 0 repeats
@kev yes, take the time to learn it from the start. The available GUIs are either so close to the #CLI, giving barely any advantage, of hide to much of the mental model of how git works. Only GUI I liked (did my first git steps with it) is TortoiseGit (windows only).Also make sure you have a relatively recent tutorial, there has been some work in the recent past for improving the CLI (not using git checkout --flagXYZ for many different actions, but introducing action-specific subcommands)
(DIR) Post #9upj7l9iv7quMUOSoK by mcepl@floss.social
2020-05-08T10:05:33Z
0 likes, 0 repeats
@kev a) most editor/IDE integrations are shit and you have to understand CLI commands philosophy (I use vim-fugitive, but still you have to know what you are doing), b) staging area is your friend, learn to like it; really. c) reading https://git-scm.com/doc (or at least watching introductory videos) is really good investment.
(DIR) Post #9upj9rmBHFrHTPO0no by mcepl@floss.social
2020-05-08T10:05:59Z
0 likes, 0 repeats
@kev and of course, if you have specific questions, ask.
(DIR) Post #9upjWoeF4c1uQrcGUS by nirmal@fosstodon.org
2020-05-08T10:10:19Z
0 likes, 0 repeats
@kev Gotta say, I'm a bit angry and unstable today 😂 I think I'd put it already on your previous toot that I could be of some help to you :)So, I'm here to help! Taking your time and reading by searching it online works always rather than reading a book from page to page. I'm not against reading a book though.But I would recommend you to start somewhere like there are lot of Git Cheat-sheets out there. You could pick one and try the commands then maybe you could move on to reading a book.
(DIR) Post #9uplmGTu4X3t0XH5k0 by codesections@fosstodon.org
2020-05-08T10:35:24Z
0 likes, 0 repeats
@kev> Ok. New day and I’m less angry. Let’s give this Git shizzle another shot.… Come on, Kev. You’re a semi-clever guy, you can bloody learn Git!That's the spirit!Pro Git (which is basically the official git book) is also *really* good and freely available on the git website: https://git-scm.com/book/en/v2
(DIR) Post #9upxVTDAggaH15Cro0 by fritogotlayed@fosstodon.org
2020-05-08T12:46:55Z
0 likes, 0 repeats
@kev For what it's worth here's a "git cheatsheet" I constructed for my co-workers when teaching them how to use git from the terminal. It assumes you're working with a fork against an upstream so there are parts you can ignore. It still may provide some value 🙂 Happy Learning!https://docs.google.com/document/d/1kX7IeC-258lWLOelxwZ9goMWnA6P6HxXlT1Hxp5TEmg/edit?usp=sharing
(DIR) Post #9upzbbFxtAgPc6Z1HM by JayT@fosstodon.org
2020-05-08T13:10:20Z
0 likes, 0 repeats
@kev the site that helped me is https://learngitbranching.js.org/It has a graphical representation of what got is doing with the commands
(DIR) Post #9uq2g8M74Jg9I1IEPw by WhoNeedszZz@fosstodon.org
2020-05-08T13:44:53Z
0 likes, 0 repeats
@kev It's a topic of hot debate, but personally I would suggest avoiding rebasing. It re-writes history and that has the tendency to cause a lot of headaches when you're working with multiple branches (which you should be). Merging, on the other hand, preserves the history and avoids a lot of merge conflicts.
(DIR) Post #9uq3OXdKRqEaQdWLxo by phillipcouto@fosstodon.org
2020-05-08T13:52:47Z
0 likes, 0 repeats
@kev You got this, when I first heard of Git it was my first encounter with source code control and I actually learned SVN instead. After a while I realized how powerful and simple decentralized repositories were. Every clone was a full independent copy that serves as a backup if need be. Now I can't imagine starting a project without it.If you really feel like getting nerdy I am sure you will find the storage technology interesting and how it diffs and packs only deltas.
(DIR) Post #9uqBMblcuHs0IszVgW by jordan31@fosstodon.org
2020-05-08T15:22:09Z
0 likes, 0 repeats
@kev If you can pacify a wife that speaks of "your jobs" then you can do just about anything. Not a lot is tougher than that.