Repository navigation
Keep a paused issue.md edit through a late update - #257
Merged
MHohlios merged 1 commit intoNov 2, 2026
Merged
Conversation
…move An older release that pulled a teammate's move wrote GitHub's files into the folder and kept its paused issue.md edit at the old path. Adopting the move then left that edit behind and dropped its pause. A file left at the root now replaces the folder's copy unless it is a stub, so the next pass pauses the edit again at its moved path.
MHohlios
deleted the
wiffletree/keep-a-paused-issue-md-edit-through-a-late-updat
branch
November 2, 2026 21:10
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.
A Mac on an older release that pulls a teammate's move writes GitHub's moved files into the Space's folder but keeps its paused edit at the old root path. After it updates, the move step skipped any root file whose folder path already existed, so the edit stayed at the root where nothing reads it, and the next pass cleared the pause. The edit was lost.
folder::move_filesnow lets a file left at the root replace the folder's copy, unless the root copy is a forwarding stub. The copy it replaces is GitHub's committed content, so nothing is lost: the next pass pauses the edit again at its moved path (OutsideWiffletree) and shows it in the Inbox, with GitHub's version as theirs.A follow-up to #235.
Tests:
a_pause_an_older_host_kept_through_a_teammates_move_follows_its_file_after_the_update. An older-layout clone with a pausedissue.mdedit pulls a move and then runs the new release's first pass; the edit is still paused at its moved path. It fails without the fix (no pause left).Follow-ups
Reviewed with Wiffletree: 1 full review and 0 re-checks, 1 round (Tests, Claude, Style)