fleet-tidying-files

To clean up untracked junk files across multiple repositories, run the tidy-files script to sweep fleet repositories for stray temporary directories and junk patterns. It operates in dry-run by default to safely identify targets before applying deletions.

Continuous maintenance workflow cleanup is handled by sweeping fleet repositories for junk files using a guarded safeDelete mechanism. This ensures deletions are restricted to untracked paths outside submodules, preventing accidental loss of tracked project data.

Real deletions of untracked junk files are applied using the optional --fix mode flag. The script defaults to a dry-run for safety, and appending --fix forces the actual removal of identified temporary directories across the repositories.

Fleet cleanup explicitly avoids removing files inside git submodules. The sweeping mechanism ensures safety by targeting only untracked junk patterns outside submodules, preventing any unintended modifications to nested repository dependencies.

Periodic cleanup before cascading commits is best executed by running the tidy-files script across the fleet. This loopable maintenance workflow removes untracked junk patterns from repositories in a dry-run state before finalizing your commit cascade.

A dry-run for junk file cleanup should be used by default to verify identified untracked paths before executing real deletions. This guarded approach prevents accidental data loss when sweeping multiple repositories for temporary directories.