Environment
- Lore:
0.8.3+201
- Platform: Windows
Reproduction
- Create and publish a merge revision using
lore branch merge into.
- Sync to the published revision:
lore sync <revision> --remote
- Inspect the state:
lore status
lore branch info
- Run sync again:
Expected behavior
Syncing to the published revision should update both the working copy and the local branch pointer.
Actual behavior
The working copy moves to the correct branch and revision, but lore status reports:
Local branch is behind remote
lore branch info shows the previous revision under Latest and the merge revision under Remote Latest.
Running lore sync again reports:
Already on branch ... latest revision ...
The local pointer remains unchanged, leaving sync and status reporting contradictory states.
Recovery and side effects
The pointer had to be reconciled manually:
lore branch reset <revision>
Afterward, lore status correctly reported that the local branch was in sync with remote.
No tracked or staged changes were present.
Notes
Synchronizing by remote revision updates the working copy but does not update the local branch's Latest pointer.
Environment
0.8.3+201Reproduction
lore branch merge into.Expected behavior
Syncing to the published revision should update both the working copy and the local branch pointer.
Actual behavior
The working copy moves to the correct branch and revision, but
lore statusreports:lore branch infoshows the previous revision underLatestand the merge revision underRemote Latest.Running
lore syncagain reports:The local pointer remains unchanged, leaving
syncandstatusreporting contradictory states.Recovery and side effects
The pointer had to be reconciled manually:
Afterward,
lore statuscorrectly reported that the local branch was in sync with remote.No tracked or staged changes were present.
Notes
Synchronizing by remote revision updates the working copy but does not update the local branch's
Latestpointer.