I've known about this for a while but I don't think there's an issue to track it
We still get too many "project has diverged" warnings on sync. So far as I know Mutchi is routinely passing -f to bypass it.
I think version hash drifts is one big problem. Once the hash algorithm updates then everything starts to look like divergence.
I think there's something wrong as well when checking out different deploys of the same project. This just created an invalid divergence:
- Pull a project
- Deploy it with --new. The new project is now checked out
- checkout the og project. I just got a divergence warning
It might be a little more subtle than that, there may have been an edit. But basically when checking out a local project that's synced to the the remote, you shouldn't get a warning for any changes. There were no local changes.
I've known about this for a while but I don't think there's an issue to track it
We still get too many "project has diverged" warnings on sync. So far as I know Mutchi is routinely passing
-fto bypass it.I think version hash drifts is one big problem. Once the hash algorithm updates then everything starts to look like divergence.
I think there's something wrong as well when checking out different deploys of the same project. This just created an invalid divergence:
It might be a little more subtle than that, there may have been an edit. But basically when checking out a local project that's synced to the the remote, you shouldn't get a warning for any changes. There were no local changes.