Git introduces interactive command to split existing commits into two

Git now provides a native command to split an existing commit into two. The `git history split` command interactively prompts the user to decide which hunks belong in the first commit, then opens an editor for both commit messages. This replaces a long-standing manual process that required staging partial changes, committing, and resetting, steps that were easy to misorder or forget.

The cost of adoption is minimal for users already familiar with Git’s interactive workflows. The command follows the same hunk-by-hunk selection pattern as `git add -p`, so engineers who use interactive staging will recognize the interface. However, the command is new and may not yet be available in all distributions or versions of Git, so teams may need to update their tooling to use it.

The feature stops working when the commit contains changes that cannot be cleanly split into hunks, such as binary files or large refactors where lines are tightly coupled. In these cases, users will still need to fall back to manual staging or external tools. The command also does not handle splitting a commit into more than two parts, so complex history rewrites will still require multiple invocations or manual intervention.

The introduction of this command reflects a shift in Git’s approach to history editing. Previously, such operations were left to third-party tools or Stack Overflow answers, but Git is now incorporating more of these workflows natively. This may reduce reliance on external scripts or outdated forum advice, but it also means engineers will need to relearn some tasks as Git’s built-in tooling evolves.