{"version":"2.1.282","anchor":"directory-sync-now-honours-gitignore-files-in-subdirectorie","canonical_anchor":"directory-sync-now-honours-gitignore-files-in-subdirectorie","heading":"Directory sync now follows .gitignore files in subfolders","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-now-honours-gitignore-files-in-subdirectorie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Directory sync now follows .gitignore files in subfolders\n\nDirectory sync now applies the .gitignore in each subfolder, not just the top-level one, and leaves out a folder whose .gitignore it cannot use\n\n**What**\n\nDirectory sync is the feature that uploads a folder from your machine for a cloud session. It now reads the `.gitignore` file (a list of files git should ignore) in every subfolder and applies it to that part of the tree, alongside the top-level rules. Before, only the top-level rules were used.\n\nThere are limits:\n\n- If the subfolder `.gitignore` files together are too large, listing fails with \"the .gitignore files in this folder's subdirectories together hold more than sync reads\".\n\n- If a subfolder's `.gitignore` cannot be read or used, that whole subfolder is left out of the sync and you are warned.\n\n**Why**\n\nCloud sessions started from a folder no longer upload files that a nested `.gitignore` excludes, such as build output inside a subpackage. Watch for the warning if a folder you expected is missing from the session.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}