this post was submitted on 24 Feb 2026
34 points (97.2% liked)

Git

4568 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago
MODERATORS
Ategon@programming.dev
canpolat@programming.dev
jnovinger@programming.dev
34
What do you use to communicate with your git repositories? (lemmy.dbzer0.com)
submitted 5 days ago by altkey@lemmy.dbzer0.com to c/git@programming.dev
35 comments fedilink hide all child comments
 

Do you use some GUI, TUI, terminal commands, plugins for other software?

Ideally, I want to find a cross-platform GUI app, preferably a FOSS one, and with as less overhead as possible, e.g. no Electron.

you are viewing a single comment's thread
view the rest of the comments
[–] spartanatreyu@programming.dev 1 points 5 days ago

Fork.dev on Windows and Mac

  • GUI using native APIs, no electron
  • It's free the same way that sublime text and winzip are. It asks about once a month if you want to pay and you can keep clicking "I'm still trying it out".
  • Normal git cli is powerful but with a terrible UI with terrible defaults.
    • To use the best commands you need to add a ton of flags to get what you want, or add a whole bunch of aliases and port them between machines.
      • e.g. git log vs git log --graph --all --remotes --decorate
      • e.g. git fetch vs git fetch --prune --all
      • e.g. git stage -p vs nothing (git cli still doesn't have a good way to specify lines correctly, only hunks that can't be split properly)

Fork.dev is just what you get when the defaults are set up correctly by default, with more powerful control over staging, and with automatic branch/stash backups whenever your doing risky actions.

The only thing it doesn't have built in support for is git log -S for when you're searching for a specific file or commit and don't know the file or commit, but know a substring in the commit itself. But it doesn't matter since you can add that as a custom command into fork.dev