What did you do before the bug happened? (Steps to reproduce your issue)
1. Create a new worktree with `git worktree add new-worktree` 2. Modify files in the new worktree 3. Move new worktree back to main working tree (i.e. master)
What did you expect to happen? (Expected behavior)
I expected uncommited changes from `new-worktree` to merge with changes from `master`
What happened instead? (Actual behavior)
The changes from `new-worktree` were lost
What's different between what you expected and what actually happened?
The uncommited changes were lost instead of preserved
Anything else you want to add:
I lost 4 hours of work :(((
Please review the rest of the bug report below. You can delete any lines you don't wish to share.
[System Info] git version: git version 2.39.3 (Apple Git-145) cpu: arm64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Darwin 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000 arm64 compiler info: clang: 15.0.0 (clang-1500.1.0.2.5) libc info: no libc information available $SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks] pre-push