A new Go-based implementation of Git's interactive add functionality has caught the attention of developers, not just for its enhanced features, but for the community discussion it has sparked about potentially replacing Git's original Perl implementation upstream.
The Go port recreates the familiar git add -i and git add -p commands while adding several powerful enhancements. These include global filtering across all files using regex patterns, automatic hunk splitting, and bulk operations that can accept all matching hunks at once. The tool maintains full compatibility with Git's existing color configuration and supports all major patch modes.
Enhanced Commands Over Original Perl Version:
G <regex>- Global filtering across all files using regex patternsG- Clear filter with interactive prompt for new patternS- Auto-splitting to enable maximum granularity globallyA- Accept all hunks across all files after filtering and splitting
Community Interest in Upstream Integration
What's particularly interesting is the community's immediate focus on getting this implementation into Git's main codebase. One developer directly asked why the author hadn't submitted it to the Git mailing list for upstream consideration. This question highlights a common desire in the developer community to see modern, enhanced tools replace older implementations in core software.
However, the reality of upstream integration proves more complex. The Git project's conservative approach to new dependencies means adding Go as a requirement would face significant resistance. As one commenter noted, it would require massive effort to align maintainers on introducing a new language, similar to the challenges faced when adding Rust to the Linux kernel.
The suggestion to just rewrite in C demonstrates the typical response to such situations, though this carries substantial weight beyond simple language translation. The implementation would need to integrate with Git's existing patch generation systems and maintain compatibility across all supported platforms.
Enhanced Workflow Capabilities
The Go implementation's standout features address real workflow pain points. The global filtering system allows developers to quickly locate specific types of changes across their entire changeset. For example, filtering for TODO comments or console.log statements can help developers stage related changes together, regardless of which files contain them.
The auto-splitting feature takes Git's existing hunk splitting capability to its logical conclusion, automatically breaking down changes to the finest possible granularity. Combined with the bulk accept feature, this creates powerful workflow combinations that weren't possible with the original Perl implementation.
Supported Patch Modes:
- Stage mode:
git add -porgit add --patch - Reset mode:
git reset -p - Checkout mode:
git checkout -p - Stash and worktree operations
- All modes support the enhanced filtering and splitting features
Alternative Tools and Ecosystem
The discussion also revealed the diverse ecosystem of Git enhancement tools that developers rely on. Several community members mentioned their preferred alternatives, including the long-established tig for terminal-based Git operations and scmpuff for enhanced staging workflows. This suggests that while the standard Git tools work, there's clearly appetite for improved user experiences.
The author's humorous response about revisiting upstream integration in 2045 reflects the realistic timeline for major changes to core Git functionality, while still expressing genuine interest in eventually replacing the upstream version.
Installation Methods:
- Direct build:
go build - Install as Git command:
go build -o "$(go env GOPATH)/bin/git-add-interactive" - Add to Git exec path:
export GIT_EXEC_PATH="$(go env GOPATH)/bin:$GIT_EXEC_PATH" - Verification:
which git-add-interactiveand test withgit add -i
Looking Forward
This project represents more than just another Git tool - it demonstrates how modern implementations can enhance familiar workflows while maintaining compatibility. The community's immediate interest in upstream integration shows there's real demand for these improvements to reach all Git users, not just those willing to install additional tools.
Whether through eventual upstream adoption or continued development as a standalone tool, this Go implementation highlights the ongoing evolution of developer tooling and the community's desire for enhanced, efficient workflows.
Reference: Git Add Interactive (Go Implementation)