Repository navigation
fix(host): untracked files don't block a move to a cloud workspace - #495
Merged
Merged
Conversation
…nd refusals name changed files Why: apps/host/src/compute.ts#function lanes | lane clones ignored files like node_modules into worktrees whose branch may not ignore them, so only tracked changes may block a move
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
1 participant
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.
Found in the move study (M3): moving a channel to a cloud workspace was refused with "mv-note (uncommitted changes)" even after the lane was committed and pushed. lane clones the project's ignored files (here
node_modules) into worktrees by reference, and the lane's branch didn't ignore them, sogit statusreported them untracked.Checked against a scratch repo: a pushed lane with an untracked
node_modules/passes; unstaged and staged edits are refused with the file named.Built in Ace
No. Written in Claude Code while it led the move study, since the Mac's Ace Canary was the build under test. Dogfooding gap tracked in #5.