It still thinks that the upstream is at the previous sha.
Current know upstream sha is together with the local sha that gives the same configuration. However, currently it pushes all local changes, including those that haven't been snapshottet yet, so no local snapshot may exist.
Automatically creating a snapshot could fix it, but I'm not too fond of that.
Only pushing "up to" a given snapshot is another solution, but the UI needs to be tight, so it's obvious that it's "up to", and not just the given changeset. Both options could be handy, but the possibility for confusion is great (the difference between pushing a changeset and a snapshot is small).
It still thinks that the upstream is at the previous sha.
Current know upstream sha is together with the local sha that gives the same configuration. However, currently it pushes all local changes, including those that haven't been snapshottet yet, so no local snapshot may exist.
Automatically creating a snapshot could fix it, but I'm not too fond of that.
Only pushing "up to" a given snapshot is another solution, but the UI needs to be tight, so it's obvious that it's "up to", and not just the given changeset. Both options could be handy, but the possibility for confusion is great (the difference between pushing a changeset and a snapshot is small).