{"version":"2.1.282","anchor":"directory-sync-gitignore-refusals-new-busy-and-too-many","canonical_anchor":"directory-sync-gitignore-refusals-new-busy-and-too-many","heading":"File sync gives two new reasons for not trusting a .gitignore","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-gitignore-refusals-new-busy-and-too-many","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### File sync gives two new reasons for not trusting a .gitignore\n\nDirectory sync now says when it skipped a .gitignore because the file was busy or because it holds too many rules\n\n**What**\n\nA `.gitignore` file lists files that git, the version control tool, should leave out. Directory sync now has two more reasons for not trusting one:\n\n- the file could not be read just then because it was busy or in use by another program\n\n- together with the `.gitignore` files above it, it holds more rules than sync applies to one path\n\n**Why**\n\nWhen sync skips a `.gitignore`, the message now says which of these happened.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}