Files
Sameen Karim fcacfc9f6c Point at --abort when a paused rebase loses its stack
If the stack file changes while a rebase is paused on a conflict — a branch
removed, the stack unstacked — `gh stack rebase --continue` failed with a bare
"no stack found for branch X". The recovery state is still on disk at that
point and `--abort` still restores everything, but nothing said so.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: f5959297-80fd-4732-aeae-aa9a4b6a7755
2026-07-27 13:15:04 -04:00
..
2026-07-15 12:07:46 -04:00
2026-04-10 03:32:08 -04:00
2026-05-15 14:01:02 -04:00
2026-05-15 14:01:02 -04:00
2026-07-15 12:07:46 -04:00
2026-07-26 11:26:04 -04:00
2026-04-10 03:32:08 -04:00
2026-05-15 14:01:02 -04:00
2026-06-15 13:54:20 -04:00
2026-06-15 13:54:20 -04:00
2026-05-15 14:01:03 -04:00
2026-07-26 11:26:04 -04:00
2026-04-20 11:20:27 -04:00
2026-05-15 14:01:02 -04:00
2026-04-10 03:32:08 -04:00
2026-07-15 12:07:46 -04:00