Community
Participate
Working Groups
Attempting a rebase that fails due to checkout conflicts (e.g. modify a workspace file that is modified in upstream) leaves the rebasing temporary files in the repository so the repo state is no longer SAFE. This has the result that egit performs a rebase --abort on the repo which subsequently overwrites local workspace changes.
To see this problem in eclipse; 1. create file.txt & commit on master 2. create branch side 3. modify file.txt & commit on master 4. checkout side 5. modify file.txt 6. rebase side onto master The rebase will file with a conflict on file.txt however the local change to file.txt will be overwritten.
(In reply to comment #1) > To see this problem in eclipse; > > 1. create file.txt & commit on master > 2. create branch side > 3. modify file.txt & commit on master > 4. checkout side 4a) modify and commit change to file.txt > 5. modify file.txt > 6. rebase side onto master > > The rebase will file with a conflict on file.txt however the local change to > file.txt will be overwritten.
Proposed fix; http://egit.eclipse.org/r/#change,3499
If8b758fde73ed5a452a99a195a844825a03bae1a has been merged and resolves this problem.