fix(git): restore checkout after update-project-files push flows#60
Merged
Conversation
MCamner
marked this pull request as ready for review
July 20, 2026 17:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The previous regression test exercised the restore helper directly and could also select the real checkout because
mq-git-menu.shassignsCURRENT_REPOwhen it is sourced. The real protected-push flows could therefore still leave the checkout on anmq/update-project-files-*branch when interrupted.What Changed
INTandTERMsynchronously in both Git launcher implementationsMQ_GIT_REPOpointing at a disposable repositoryVerification
tests/git-restore-to-base-smoke.shproves restoration after a successful push, a push failure, andTERM. Each scenario ends onmainwith a clean tree andmainmatchingorigin/main.tools/scripts/test-all.shpasses, including shell lint for 160 files.