Sync: invalid divergence warnings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the sync divergence check and reproduce the reported sequence: pull a project, deploy it with --new, then check out the original project. Compare that behavior with version-hash changes and the -f bypass; done means a synced project with no local edits produces no invalid divergence warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100