GIT - is it me or is it just really horrible?

[NickFitz]

Git is a complete pain, yet also excellent for the purposes it serves

One useful resource is Oh tulip, Git!?! (I had to link to the SFW version "Dang it, Git!?!" as the naughty words filter broke the URL) which explains how to get yourself out of numerous common situations. But they're all in terms of the command line.

If you crave a deeper understanding of how Git works, which is definitely helpful in figuring out what's going on, then the official Git book is the place to start.

I used to use SourceTree but haven't in a while, as I use JetBrains IDEs these days and they have their own UIs for dealing with Git. I still regularly cock things up, but I have a slightly better idea now of how to recover.

[_V_]

If you are using Visual Studio Code as your code editor it has Git source control built in. Just add something like Git lens and you can see file history etc in the code editor directly.

https://marketplace.visualstudio.com...amodio.gitlens

[_V_]

Git is great, sourcetree is not a great UI.

This is a better GUI for Git.

https://www.gitkraken.com/

[Dark Black]

To add some balance to this - I couldn't disagree more. Been developing software and using some form of source control for 12 years, so not ages - but long enough to know that there's nothing wrong with an intuitive UI. It's not 'elite' to use commands if visualisations work for you personally (granted, doesn't work for everyone). I would say you need an appreciation for the git commands the likes of sourcetree is automating, but nothing wrong with sourcetree (or any other similar git client).

What, specifically, are you struggling with in GIT Dark Black ? I'll see if I can help you at all, but there are only a handful of concepts/commands you need to be familiar with.

It's specifically with my understanding of the SourceTree GUI when it comes to switching branches - I'll post tomorrow when I've got ST up on the laptop and can explain what my issues are!

[d000hg]

I use SourceTree on one project. I quite like it, as it enforces a workflow. I hate Git command line though.

The thing I find hardest is understanding the history, you just see something a bit like a map of the London Underground.

[NotAllThere]

It's not just you. I've never got to grip with git. It's well named.

[Paralytic]

Your comment makes 0 sense in the current context. What have git commands got to do with lines of code?

Someone needs a git revert...

[cannon999]

The era of measuring lines of code as a proxy for productivity in software development died 20 odd years ago.

Your comment makes 0 sense in the current context. What have git commands got to do with lines of code?

[eek]

It's not about the eliteness, it's about speed. I will bash out git commands faster than you can click your GUI buttons all day long. Given that this is something you have to do day in, day out and is an integral part of your job - you are less productive than I am as a developer.

The era of measuring lines of code as a proxy for productivity in software development died 20 odd years ago.

[cannon999]

To add some balance to this - I couldn't disagree more. Been developing software and using some form of source control for 12 years, so not ages - but long enough to know that there's nothing wrong with an intuitive UI. It's not 'elite' to use commands if visualisations work for you personally (granted, doesn't work for everyone). I would say you need an appreciation for the git commands the likes of sourcetree is automating, but nothing wrong with sourcetree (or any other similar git client).

What, specifically, are you struggling with in GIT Dark Black ? I'll see if I can help you at all, but there are only a handful of concepts/commands you need to be familiar with.

It's not about the eliteness, it's about speed. I will bash out git commands faster than you can click your GUI buttons all day long. Given that this is something you have to do day in, day out and is an integral part of your job - you are less productive than I am as a developer.