What
File sync, which copies a project into a cloud session, now checks the project's git data (the .git folder holding its history) before going ahead. It refuses and explains why when:
- an item stored in git does not match the name it is filed under, which git itself never produces
- the history holds a folder listing in an old format that git can read but does not write
- it cannot create its own private working folder
- the
.gitignorefiles in the folder's subfolders together hold more than sync will read
The messages point to git fsck, git's own checking tool, to find the item at fault. Before, the only such check was for planted links.
Why
When a cloud session will not start because of the project's git data, you now get a message saying what is wrong instead of a refusal you cannot diagnose.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The size limits for the combined `.gitignore` files are not known.