You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Directory SyncArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
Unclear The finding does not say what situation triggers the new host_config refusal.
What
File sync sometimes refuses to work with a project. One reason is a problem with .git/info/attributes, a Git file that holds per-project rules about how files are treated. The refusal message for that file now names the kinds of line file sync cannot vouch for:
a filter or encoding rule
an attribute macro
a quoted pattern
The message also covers the case where the file cannot be read as a plain file.
There is also a new refusal case called host_config. Its message shows a reason passed along with the refusal. It goes with a new hostConfig field in the result that file sync reports after applying changes.
Why
If file sync refuses a project because of .git/info/attributes, the message now tells you which kinds of line to look for, so you know what to check or remove.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what situation triggers the new `host_config` refusal.