{"version":"2.1.281","anchor":"file-sync-rewritten-gitinfoattributes-error-and-new-host","canonical_anchor":"file-sync-rewritten-gitinfoattributes-error-and-new-host","heading":"File sync: rewritten .git\/info\/attributes error and new host_config refusal","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/file-sync-rewritten-gitinfoattributes-error-and-new-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### File sync: rewritten .git\/info\/attributes error and new host_config refusal\n\nFile sync's refusal about .git\/info\/attributes now names the problem lines, and a new host_config refusal is added\n\n**Unclear.** The finding does not say what situation triggers the new `host_config` refusal.\n\n**What**\n\nFile 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:\n\n- a filter or encoding rule\n\n- an attribute macro\n\n- a quoted pattern\n\nThe message also covers the case where the file cannot be read as a plain file.\n\nThere 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.\n\n**Why**\n\nIf 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."}