Alternatives
Products that do what 'git inject' – amend commits other than HEAD does
'git inject' is a git alias (see code at the bottom). It is similar to 'git commit --amend', but it allows you to 'inject' your changes into commits further back in history (using 'rebase'). If you're as pedantic as I am about the git history you're about to push into master (as far as I can control it, I strive to keep each commit conceptually coherent), you'll often come to a situation where you have a modification that really belongs in an older commit. It takes a few git commands to stash other changes away, commit the modification, then interactively rebase over some previous commit,…
- 1GF
2016 · github.com
- 2

- 3RE
2017 · github.com
- 4

- 5

- 6RI
2015 · gist.github.com
- 7

- 8

- 9

- 10

- 11GRGit-Retext▲33
2020 · blog.aloni.org
- 12

- 13GS
Hunk-by-hunk and line-by-line staging for git, designed for building clean commit history! Writing code is messy. Git history doesn't have to be. During development we experiment, refactor, backtrack, and fix mistakes. If every step ends up as a commit, the history becomes noise. A curated history turns that process into a clear sequence of logical changes. git-stage-batch helps you build that history incrementally by letting you stage changes hunk-by-hunk or line-by-line, shaping commits around meaning instead of the order the edits happened.
Apr 2026 · github.com
- 14

- 15GN
Hey HN, I built a VS Code extension that lets you do Git things without memorizing Git commands. You know what you want to do, move this commit over there, undo that thing you just did, split this big commit into two smaller ones. Git Navigator lets you just... do that. Drag a commit to rebase it. Cherry-pick (copy) it onto another branch. Click to stage specific lines. The visual canvas shows you what's happening, so you're not guessing what `git rebase -i HEAD~3` actually means. The inspiration was Sapling's Interactive Smartlog, which I used heavily at Meta. I wanted that same experience…
Feb 2026 · gitnav.xyz
- 16

- 17

- 18

- 19IW
2020 · rebase-book.com
- 20TB
2018 · github.com
- 21GC
2016 · github.com
- 22GL
2020 · github.com
- 23RA
I really like interactive rebases in Git, but always thought they took too much time and effort. There are tools that make them a lot nicer, like magit or GitUp, but they still ask a lot of you. So over the last two years I built Retcon. In the app, you can manipulate history directly (e.g. drag a commit to a different spot) at all times; even when there’s a conflict waiting for resolution, you can always keep making changes. You're not asked to first make a rebase TODO and then commit to it. So you no longer need to think too much ahead: you just make the changes you have in mind, see what…
2024 · retcon.app
- 24RP
After some feedback I spent some time re-reading through the git docs, and refactored to add time tracking data into the commit message directly. It's simpler than using tags. thanks.
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →