this post was submitted on 09 Nov 2023
1081 points (98.1% liked)

Programmer Humor

32480 readers
284 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
(page 2) 31 comments
sorted by: hot top controversial new old
[–] kaffiene@lemmy.world 2 points 1 year ago

This week? I've been using it for years and I'm still learning it

[–] m3t00@lemmy.world 1 points 1 year ago
[–] dan@upvote.au 1 points 1 year ago* (last edited 1 year ago) (3 children)

Honestly, just use a GUI. Graphical user interfaces were designed for a reason. I usually use SourceTree or the Git functionality built in to Visual Studio or VS Code.

It's good to know how things work under-the-hood (e.g understand Git's object model, some basic commands, etc) but don't feel like you need to use the command-line for everything.

[–] kamen@lemmy.world 1 points 1 year ago

My take is use a GUI for anything read-only/nondestructive (i.e. anything that won't modify your local or remote state). It's nice for example to compare the state of two branches.

For anything that does changes make sure you know what's happening under the hood, otherwise you might shoot yourself in the foot. It's convenient for example to do a commit and push in one go, but then you lose the ability to edit any changes (you're forced to either do another commit, or change your local commit and force push).

In VSCode you can go to the Output pane and switch to Git - there you'll see everything that gets done through Git's CLI for whatever you do through the GUI (although it can be a bit noisy); same goes other GUI utils.

load more comments (2 replies)
[–] Imbrex@lemmy.world 1 points 1 year ago

so do ya'll like git or git in a hub?

load more comments
view more: ‹ prev next ›