{"version":"2.1.246","anchor":"directory-sync-rewrites-awkward-gitignore-lines-instead-of-g","canonical_anchor":"directory-sync-rewrites-awkward-gitignore-lines-instead-of-g","heading":"Directory sync rewrites awkward .gitignore lines instead of giving up on the file","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/directory-sync-rewrites-awkward-gitignore-lines-instead-of-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Directory sync rewrites awkward .gitignore lines instead of giving up on the file\n\nOne awkward .gitignore line no longer makes sync reject the whole file.\n\n**What**\n\nIgnore lines that sync previously could not match are now rewritten where possible rather than rejected, so a single tricky line no longer makes the whole `.gitignore` count as too complex to use.\n\n**Details**\n\n- Trailing blanks and unicode spaces, bracket expressions, escapes and case-folding differences are normalized.\n- Rewritten lines are reported as `adjusted` with a reason of either \"wildcards\" or \"spelling\", and are marked internally as having been widened, so sync knows where it now matches more than git would.\n- Applies to directory sync only.\n\n**Evidence**\n\n`a bracket expression, an escape or a trailing blank that sync reads differently from git`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}