A CLI tool written in Rust to track and analyze multiple Git repositories concurrently.
gfold is a command-line tool that helps developers keep track of multiple Git repositories by displaying their status and relevant information in one consolidated view. It solves the problem of managing scattered Git projects by providing a quick, read-only overview without modifying any files. The tool is built in Rust for performance and leverages concurrent analysis to efficiently scan directories.
Developers and system administrators who work with multiple Git repositories across different directories and need a fast, non-invasive way to monitor their status. It's particularly useful for those managing monorepos, personal project collections, or complex development environments.
Developers choose gfold for its speed, safety, and simplicity—it performs concurrent read-only analysis without risking repository modifications. Its focus on a single purpose, cross-platform compatibility, and easy configuration via TOML files make it a reliable alternative to manual Git status checks across multiple projects.
CLI tool to help keep track of your Git repositories, written in Rust
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Rayon for concurrent, read-only analysis of all detected Git repositories, enabling fast status checks across multiple directories as highlighted in the README.
Only reads from the filesystem and never writes, ensuring no accidental modifications to repositories, which is a core design philosophy stated in the description.
Supports classic and default display modes with configurable color settings via TOML config files, allowing persistent preferences as shown in the config examples.
Runs on any tier-one Rust target and is installable via package managers like Homebrew, Cargo, and pacman, with wide compatibility as noted in the installation section.
Intentionally limited to status display without Git command execution, filtering, or advanced metrics, which might not suffice for complex repository management needs.
Requires setting up TOML config files for persistent settings, adding setup steps compared to tools with built-in defaults or simpler CLI options.
On macOS, naming collisions with coreutils can occur, necessitating workarounds like aliases or PATH changes, as mentioned in the troubleshooting section.