this post was submitted on 13 Dec 2023
486 points (94.2% liked)

Programmer Humor

19589 readers
416 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
486
GitHub Desktop or Git CLI? (programming.dev)
submitted 11 months ago by hypnotic_nerd@programming.dev to c/programmer_humor@programming.dev
157 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] derpgon@programming.dev 33 points 11 months ago (4 children)

JetBrains IDEs, I don't remember the last time I used the CLI.

[–] caseyweederman@lemmy.ca 38 points 11 months ago (1 children)

you have forgotten the face of your father

[–] QuazarOmega@lemy.lol 10 points 11 months ago

Linus Torvalds?

[–] eluvatar@programming.dev 3 points 11 months ago

This is the way

[–] CodingCarpenter@lemm.ee 2 points 11 months ago

I was looking for this comment. PHP storm and git are like best friends. I very very rarely need to resort to the CLI and generally that's for hard resetting after I screw something up

[–] expr@programming.dev -5 points 11 months ago (4 children)

Good luck doing anything remotely complicated/useful in git with an IDE. You get a small fraction of what git can do with a tool that allows absolutely 0 scripting and automation.

[–] calcopiritus@lemmy.world 14 points 11 months ago

IDE git is less powerful than CLI git. However I'm pretty confident that most people use more features of git by using a GUI.

CLI feature discoverability is pretty awful, you have to go out of your way and type git help to learn new commands.

With a GUI though, all the buttons are there, you just have to click a new button that you've been seeing for a while and the GUI will guide you how to use it.

[–] derpgon@programming.dev 10 points 11 months ago

It sounds like you don't speak from experience. I have all the automation I need. It supports git hooks on top of IDE-only features like code checking.

If I have to fire up my CLI for some mass history rewriting (like changing an author for every commit), or when the repo breaks - so be it. But by not using the CLI I save my fingers and sanity, because committing a bunch of files is several click away with little to no room for error.

I can rebase, patch, drop, rename, merge, revert, cherry pick, and solve conflicts with a click of a button rather than remembering all the commands and whatnot.

[–] GBU_28@lemm.ee 3 points 11 months ago

I use the cli, but my main goal is to never have to do anything remotely complicated with git. Does it happen sometimes? Of course.

[–] muddi@hexbear.net 2 points 11 months ago* (last edited 11 months ago)

There are automations. You can even add git hooks iirc. Mostly I find the lint and other code quality integrations nice to have in the IDE, since the inline results allow me to navigate directly to the code

Diffing is a lot easier too