In mercurial I created 3 diffs, each with 2 commits. I ran `arc land diff2 --hold` and saw a prompt asking if the branches should be pruned after the hold. I entered `y` and after the land completed I verified that the old merged branch was pruned and the resulting working state allowed for pushing up the new `master`. I also verified that the indication directions after the hold only indicated pushing up the changes and not how to restore back to the original state, as once the branches are pruned this is no longer possible.
I set up the same scenario and when I ran `arc land diff2 --hold` I answered `n` to the prompt. After the land completed I verified that the state of the local repo contained both the squashed commit as well as the original branch. I also verified that the instructions for the hold also included steps to restore to the original state.
I setup the same scenario again and I ran `arc land diff2` without the hold. I verified that the two revisions landed properly and the original branches were pruned.
I setup the same scenario again and I ran `arc land diff2` without the hold, but when prompted to confirm landing the revisions I answered `n` and the land workflow was cleanly aborted/stopped, verifying that existing prompt behavior is in tact.
TODO:
Same test in git