this post was submitted on 07 Aug 2025
89 points (98.9% liked)

Programming

22589 readers
93 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) 43 comments
sorted by: hot top controversial new old
[–] oantolin@discuss.online 2 points 1 month ago

I'm an Emacs users, so unsurprisingly I use magit, but perhaps surprisingly I use it sparingly, using Emacs's VC most of the time.

[–] cupcakezealot@piefed.blahaj.zone 2 points 1 month 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 month ago

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

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

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

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

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

[–] thecoffeehobbit@sopuli.xyz 2 points 1 month ago

Vscode and gitlens for routine stuff, and then just CLI when push comes to shove and I need some more advanced feature.

[–] Timberfang@pawb.social 2 points 1 month ago

I use VSCode and SourceGit. SourceGit is similar to Fork (which I've used before), but it's FOSS and cross-platform (Windows/macOS/Linux).

[–] oplkill@lemmy.world 2 points 1 month ago
[–] jerkface@lemmy.ca 2 points 1 month ago

I will install emacs on a machine just to use magit.

[–] leftzero@lemmy.dbzer0.com 2 points 1 month ago (3 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. 🤷‍♂️

[–] mr_satan@lemmy.zip 1 points 1 month ago

I second this, although I'm mostly alone with git extensions in my workplace.

I migrated to from sourcetree some years ago. At the time we had some big generated API client classes (imagine ~60k lines of code). They needed to be regenerated whenever we made changes and the diff on sourcetree was shitting the bed every time I needed to stage the damn files. It was just way too lagy, so I got fed up and moved.

On my personal machine I prefer lazygit or just plain CLI.

load more comments (2 replies)
[–] Quibblekrust@thelemmy.club 2 points 1 month ago

Vscode with the Git Graph extension.

[–] Xuntari@programming.dev 1 points 1 month ago

LazyGit and GitKraken. I try to use LazyGit as much as possible, but a few things are easier for me in GitKraken (as I'm more used to it).

[–] Shareni@programming.dev 1 points 1 month ago

Lazygit and magit

[–] locuester@lemmy.zip 1 points 1 month ago

Git Graph VS Code extension

I’ve used source tree, gitkraken, etc. this simple extension is just as good. I spend most my day with it

[–] astrsk@fedia.io 1 points 1 month 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.

[–] HaraldvonBlauzahn@feddit.org 1 points 1 month ago
[–] TomasEkeli@programming.dev 1 points 1 month ago

vscode with edamagit and the cli

[–] koala@programming.dev 1 points 1 month ago

When I learned Git I think there were not decent tools, so I got used to the command line.

I occasionally use gitk for reviewing my commits- it's nicer to see the files modified and be able to jump back and forth, although I get I could use git log -p instead.

I'm an Emacs user, but I don't use magit (!)

I like some of the graphical tools- some colleagues use Fork and I like it... but as I've already learned the CLI, I don't see the point for me.

I could use learning some jj because it automates some of the most tedious parts of my workflow, but I'm getting too old.

[–] dil@lemmy.zip 1 points 1 month ago

Tried idea community edition, honestly not bad, like vs code slightly more even tho with an extension or two you can make how they function very similar. Wanted to use idea because it matched the gtk theme, but if I was gonna use an extension for vs code like navigation might as well use vs code. Both easy to use with git as a dabbler.

[–] locuester@lemmy.zip 1 points 1 month ago

Git Graph VS Code extension

I’ve used source tree, gitkraken, etc. this simple extension is just as good. I spend most my day with it

[–] ruffsl@programming.dev 1 points 1 month 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.

[–] fulg@lemmy.world 1 points 1 month ago* (last edited 1 month 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.

[–] catalyst@lemmy.world 1 points 1 month 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)
[–] Cratermaker@discuss.tchncs.de 1 points 1 month ago

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.

[–] Tenkard@lemmy.ml 1 points 1 month ago

Github desktop, despite the name it's just a git client. Absolutely clownish that there's no official Linux support (there's a fork which works perfectly). I use it to interact with self-hosted gitea, codeberg and github, pretty happy with it, I'm Aldo testing git butler

[–] tiredofsametab@fedia.io 1 points 1 month ago

I have tortoise git on a windows machine and GitHub desktop on a Mac. I do some things from the command line when I'm not feeling lazy.

load more comments
view more: ‹ prev next ›