You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ui: warn when include patterns defeat directory pruning (#162) (6d3b4b2)
Bug Fixes
core: self-heal a stale drive_file_id when an update hits a definitive 404 (#168) (8b983b3)
Performance Improvements
core: per-directory decision cursor for the exclusion preview + NFC fast path (#172) (a587fed)
Notes
Behavior change (gitignore semantics): a !negation inside a nested .gitignore that lives inside an excluded directory no longer re-includes files from that directory. This matches git's own behavior (git does not read ignore files inside ignored directories) and is what makes safe directory pruning possible. If you relied on the old permissive re-include, move the negation to a .gitignore outside the excluded directory or use a per-source include pattern.
Anchored include patterns now enable pruning: include patterns like /*/.env or /repo/path/.env let the scanner skip excluded directories (e.g. node_modules) entirely; fully relative patterns like .env still force a full descent. The rules editor now warns about the latter.
Remote self-heal: if a backed-up file's Drive object is deleted out-of-band, Driven now detects it (at startup, on deep-verify, and on upload) and re-uploads automatically instead of erroring forever with "Drive unavailable".
io_priority (Settings -> Rules) now maps to real OS scheduling: on Windows, low runs backup CPU below normal and hints file I/O low; idle uses full background mode. Best-effort on Linux/macOS.