A terminal-based interactive interface for common Git operations with vi and mc-style keybindings.
Git Commander is a terminal-based interactive Git client that provides a visual interface for common version control operations. It allows developers to manage Git workflows—such as staging files, committing changes, viewing logs, and comparing diffs—through a keyboard-driven UI without leaving the command line. The tool simplifies Git usage for those who prefer graphical interaction over raw command-line commands.
Developers and Git users who work in terminal environments and want a more visual, interactive way to execute Git commands without switching to a full GUI application.
Git Commander offers a lightweight, keyboard-first alternative to command-line Git, reducing memorization of commands and providing immediate visual feedback. Its customizable keybindings and preconfigured vi/mc layouts cater to users familiar with those editors, enhancing productivity within terminal workflows.
A git tool with an easy terminal interface.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a navigable interface for viewing and selecting staged/unstaged files, simplifying add/reset processes without memorizing command-line syntax, as shown in the status view feature.
Offers preconfigured vi and mc-style key sets with user-configurable overrides via a JSON config file, catering to users familiar with those editors for enhanced efficiency.
Allows in-line viewing of file changes before committing, providing clear feedback on modifications directly in the terminal, as highlighted in the file diff viewer feature.
Enables listing and switching between branches from within the interface, making branch management more intuitive without leaving the terminal environment.
The README explicitly admits that git merge (with conflict handling) and git pull/push are not yet implemented, limiting its utility for full Git workflows.
Customizing settings requires manually creating and editing a config.json file at ~/.config/git-commander/config.json, which can be cumbersome for casual users.
Users may encounter issues with ANSI color codes or non-ascii characters, necessitating manual Git config changes as described in the troubleshooting section, adding setup complexity.