Repository navigation
v1.5.0
The verify gate now checks where a move or reorder is most likely to have broken a commit it never touched, and a run that has already moved the branch finishes through a signal instead of dying halfway.
A move or reorder used to verify only its tip, so a commit carried below a file its own check needs landed green whenever the tip still held that file. The default tier now also checks each commit a move or reorder puts directly below one that came before it: a commit moved down where it lands, and for a commit moved up, the commit it lands on. Every commit it jumped over that needed it keeps failing until it reappears, so that one check stops the run whichever of them broke, and the report names the moved commit as the first one above that passes again. A plain --reorder gets the same check, worked out from the old order and the new one.
Every mode now also checks the first commit it rebuilt, which a commit moved up or dropped leaves without what sat below it, and each commit a conflict resolution wrote, since git replayed the rest and a later commit can heal a wrong resolution before the tip ever shows it. The verification line says how many of the commits it ran were resolved at a stop. A replant counts only what it built, leaving out the commits its new upstream brings.
Quitting an app that started git edit – a Git GUI, an editor – takes away the reader of its output, and the run used to die on the next write without cleaning up, leaving its worktree registered. A lost reader now stops a run before the branch moves the way SIGHUP, SIGINT and SIGTERM do, and it exits 141. Once the branch's update-ref has begun, a run finishes instead – the journal entry --undo reads, the rewrite delivery and the index re-sync all still happen – and exits 0 with a line above its trailer naming the signal. A second SIGHUP, SIGINT or SIGTERM still stops it at once, with a trailer naming the move for git edit --undo.
Some checks fed text through a pipe into grep -q and missed what they looked for once it outgrew the pipe buffer, since grep exits at its first match and the writer it leaves behind fails the pipeline. --continue now refuses a staged resolution that still carries conflict markers whatever its size – from about 40 KB the markers could pass unnoticed and be committed. A batch reword of --- <commit> records is read as records however long it gets.
GIT_EDIT_ACTOR closes every reflog entry git edit writes with a label – git edit: reorder 1a2b3c4..5d6e7f8 [ci-nightly] – so a history viewer can name who moved the branch. --exec's reflog entry names the oldest commit it replaced, as the other modes name their target.
brew install thomasbachem/tap/git-edit
Or brew upgrade git-edit where it is already installed, or pull the repo if its folder is on your PATH.