I mostly feel like that using the git cli is the best way to truly u derstand what git is doing. Most of the gui products I've seen are more just for people who wish to memorize what the right buttons are to click that make their code go to origin. If something goes wrong, or anything more complicated needs to happen, it becomes a problem. Obviously a lot of gui tools can handle these situations, but I haven't seen it well organized/represented in guis, and the folks using them don't tend to be ready for it. This is a huge sweeping generalization and clearly isn't always the case. Just my experience.
Thanks for sharing your experience. I can honestly say that I don't know what to do when something goes wrong, so your generalizations might not be too far off.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I mostly feel like that using the git cli is the best way to truly u derstand what git is doing. Most of the gui products I've seen are more just for people who wish to memorize what the right buttons are to click that make their code go to origin. If something goes wrong, or anything more complicated needs to happen, it becomes a problem. Obviously a lot of gui tools can handle these situations, but I haven't seen it well organized/represented in guis, and the folks using them don't tend to be ready for it. This is a huge sweeping generalization and clearly isn't always the case. Just my experience.
Thanks for sharing your experience. I can honestly say that I don't know what to do when something goes wrong, so your generalizations might not be too far off.