Victoria Dye <vdye@xxxxxxxxxx> writes: > Note that you'll also probably need to check out the file(s) (if moving into > the cone) or remove them from disk (if moving out of cone). If you don't, > files moved into cone will appear "deleted" on-disk, and files moved > out-of-cone that still appear on disk will have 'SKIP_WORKTREE' > automatically disabled (see [1]). Does it also imply that we should forbid "git mv" of a dirty path out of the cone? Or is that too draconian and it suffices to tweak the rule slightly to "remove from the worktree when moving a clean path out of cone", perhaps? When a dirty path is moved out of cone, we would trigger the "SKIP_WORKTREE automatically disabled" behaviour and that would be a good thing, I imagine?
