GitQlient vs GitUI

GitQlient is a free, multi-platform Git client written with Qt and originally forked from QGit. It can open several repositories at once, but handles each independently and has no cross-repository features. Its main view includes commits, work in progress, branches, tags, stashes, and submodules; quick actions cover pull, fetch, prune, push, and stash. Diff and blame/history views include file history and line blame. For conflicts from merge, pull, or cherry-pick operations, GitQlient opens a merge view, but conflicted files must be edited in a separate editor. The project lists GitHub and GitLab integration, including issue and pull-request creation from its platform menu, and describes an embedded text editor with C++ syntax highlighting. It works offline and is available for Linux, macOS, and Windows. The manual identifies it as free software under the GNU Lesser General Public License, version 2 or later, without warranty. The macOS DMG is available, but that version is not tested due to lack of resources.

GitUI provides a Git GUI-style workflow inside a terminal, controlled with the keyboard and supported by context-based help. Users can inspect changes and commit, amend, stage, unstage, revert, or reset at file, hunk, or line level. It also supports saving, applying, popping, dropping, and inspecting stashes. Branch tools cover creation, renaming, deletion, checkout, and remote branches, alongside pushing and fetching. Users can browse or search the commit log, inspect committed diffs, and work with submodules. Commit workflows support several Git hooks; GPG commit signing is listed with shortcomings. GitUI is free under the MIT License, which includes an as-is warranty disclaimer. Listed platforms are Android, Linux, macOS, and Windows, with desktop platform support listed for Linux, macOS, and Windows. The project README describes GitUI as beta and notes that bugs or missing features may occur, while also describing it as reasonably stable for personal use. It does not fully replace the Git shell, lacks sparse repository support, and requires explicit configuration of an HTTPS credential helper.