{"version":"2.1.282","anchor":"busy-gitignore-reads-classified-as-momentary-not-unreadabl","canonical_anchor":"busy-gitignore-reads-classified-as-momentary-not-unreadabl","heading":"A busy .gitignore file is now treated as a temporary problem","tier":"internal","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/busy-gitignore-reads-classified-as-momentary-not-unreadabl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### A busy .gitignore file is now treated as a temporary problem\n\nWhen a folder's .gitignore can't be read because it is busy, Claude Code now treats that as temporary, not as unreadable\n\n**Unclear.** It is not clear what Claude Code does differently with a momentary problem, such as whether it tries again.\n\n**What**\n\nA .gitignore file tells git which files to ignore. Sometimes Claude Code cannot use a folder's .gitignore because another program has the file busy. That case is now classed as a momentary problem, not as an unreadable file. The message you see is the same.\n\n**Why**\n\nA file that is briefly locked is no longer handled as if it could never be read.\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}