this post was submitted on 07 Aug 2025
78 points (98.8% liked)

Programming

22034 readers
317 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I'm wondering if you use any (graphical) clients to manage your Git, and if so, what client you use.

I myself have to use git professionally across all 3 major OS-es, and I currently use Sourcetree on Windows and macOS, and the Git tools built-in into IntelliJ on Linux.

Have given MaGit a try, but just couldn't get all the shortcuts to stick in my mind.

Interested to hear your experiences!

(page 2) 31 comments
sorted by: hot top controversial new old
[–] cupcakezealot@piefed.blahaj.zone 2 points 1 day ago (1 children)

i loved fork on windows but i'm too lazy to set up wine to try and get it to work now i just use git cola and the cli.

[–] zarlin@lemmy.dbzer0.com 1 points 1 day ago

I use SourceGit as a Fork alternative on Linux, it's pretty similar

[–] anas@lemmy.world 2 points 1 day ago

Mostly vscode, and GitHub desktop for projects that I don’t use vscode for. I want to learn how to use the CLI, I just didn’t get around to it yet.

[–] roadrunner_ex@lemmy.ca 3 points 1 day ago* (last edited 1 day ago)

I'm a big fan of tig for visualizing the graph and looking over history (then I don't need to leave the terminal, and it's snappier, in my experience, than most full-GUI programs like Sourcetree), but for actual Git commands, I like the CLI

[–] setsubyou@lemmy.world 3 points 1 day ago (1 children)

I mostly use the cli, but also Sublime Merge. It makes some things really convenient (like committing only some lines in a changed file), and looking at diffs is snappy too.

[–] tribut@infosec.pub 3 points 1 day ago* (last edited 1 day ago)

Just fyi, you can add only a few lines of a changed file on the cli too using git add -p

[–] kewjo@lemmy.world 3 points 1 day ago* (last edited 1 day ago) (1 children)

cli and meld for mergetool

[–] HaraldvonBlauzahn@feddit.org 3 points 1 day ago

Yeah, meld is nice.

[–] Quibblekrust@thelemmy.club 2 points 1 day ago

Vscode with the Git Graph extension.

[–] leftzero@lemmy.dbzer0.com 2 points 1 day ago (2 children)

Git Extensions.

It's what they used at my job when I started, it does the job, and I've gotten used to it. 🤷‍♂️

load more comments (2 replies)
[–] jjjalljs@ttrpg.network 2 points 1 day ago

Whatever's built into pycharm or vscode for looking at diffs. Command line for push pull squash etc

I made some automation in python for common git tasks and use the cli otherwise. I tried a couple like sourcetree and the built in automation for VS but they're either slow or lack features i'd like.

[–] tunetardis@piefed.ca 2 points 1 day ago

I use Sourcetree for routine stuff, though I occasionally have to hit the command line when shit gets real.

[–] Anafabula@discuss.tchncs.de 2 points 1 day ago

lazygit & gitsigns.nvim

Do Jujutsu & jjui count? The backend is still git.

[–] AMillionMonkeys@lemmy.world 2 points 1 day ago

I use GitHub Desktop on Mac and PC. It works fine with local repos, too.

[–] cecilkorik@piefed.ca 1 points 1 day ago

CLI and VSCodium

[–] HaraldvonBlauzahn@feddit.org 1 points 1 day ago
[–] ruffsl@programming.dev 1 points 1 day ago

Mainly the official git CLI for controlling branches and sub modules, and sometimes the GitHub CLI if quickly checking out a pull request from a forked repo.

Also use the source control tab in VSCode rather often, as it's really convenient to review and stage individual line changes from its diff view, and writing commit messages with a spell check extension.

If it's a big diff or merge conflict, I'll break out the big guns like Meld, which has better visualizations for comparing file trees and directories.

About a decade ago, I used to use SmartGit, then tried GitKraken when that came around, but never really use much of the bells and whistles and wasn't keen on subscription pricing. Especially as the UX for GitHub and other code hosting platforms online have matured.

[–] astrsk@fedia.io 1 points 1 day ago

CLI, nvimdiff 90% of the time. If I’m on a windows workstation, I might end up using git extensions GUI as it helps me visualize what’s happening a little better sometimes.

[–] catalyst@lemmy.world 1 points 1 day ago (2 children)

CLI for me. I do use the GitLens plugin in vs code but only so I can see commit info inline. I never commit anything from vs code.

I like Kaleidoscope (v3) for diffs but not for merging. I could probably use any graphical difftool for this purpose but it’s what I’m used to.

load more comments (2 replies)
[–] fulg@lemmy.world 1 points 1 day ago* (last edited 1 day ago)

For professional use I’ve heard good things about SmartGit, unfortunately my work refused to buy me a license and the trial period wasn’t long enough for me to really form an opinion.

Work suggests to use SourceTree but it is way too sluggish.

These days I use git CLI for most things, and VSCode to review changes and submit PRs. Of course this also assumes you use a decent shell with git support, like Oh-My-Posh or similar, so it is always clear what you are working on.

load more comments
view more: ‹ prev next ›