Good morning,
I have discovered a discrepancy between my local plastic repo compared to the upstream cloud repo it is set up to sync.
Attached you find two screenshots from the branch explorer, the first one is from our cloud repo, the second one is from the local
repo I have on my machine. I have labelled the relevant changesets with A, B, C and D.
Let's assume that the cloud repo shows the correct picture, the order of the changesets are A, B, C, D. My local branch explorer shows another order, A, C, D, B.
In my local repo, if I right click on the changesets and choose "Go to parent changeset" the order does in fact seem correct. parent of D is C, parent of C is B and finally parent of B is A. Does that mean that it's just the branch explorer view that is confused?
Another symptom is that green bar up at the top, it say that I have -1 changesets to sync, when I have changeset B checked out.
Could I have managed to sync the three branches in a peculiar order from the cloud to my local repo to end up in this state?
Have my local repo been corrupted somehow? Do I dare use it to push new local branches to the cloud? For example I want to create a child branch of D locally, and check some stuff in, do I dare push that upstream?
Oh yeah, I am using the legacy UI of Plastic SCM 11.0.16.7303 on Windows 10.
The new UI shows the same A, C, D, B order (although I can only make branch explorer view my local repo from there).
I will be grateful for any insight you might have.
Cheers,
Andreas