Backups Directory

This directory stores backup copies of VSCode configurations that are tracked in git for version control and sharing.

Directory Structure

backups/
├── exports/          # Exported configurations with timestamps
├── installs/         # Backups created before installation
├── originals/        # Original configurations before any changes
└── archives/         # Compressed backup archives

Backup Types

• Export Backups: Created when exporting current configuration
• Install Backups: Created before installing new configuration
• Original Backups: Preserve original state before any modifications
• Archive Backups: Compressed versions for long-term storage

Usage

The backup system is automatically used by the export and install scripts. You can also manually manage backups using:

# Create a backup
make backup

# List backups
make list-backups

# Restore from backup
make restore-backup

Version Control Integration

✅ Git Tracked: All backup files are included in version control ✅ Team Sharing: Backups are shared across team members
✅ History: Full backup history preserved in git ✅ Collaboration: Team members can access and restore shared backups

Security Note

⚠️ Important: Since backups are now tracked in git, ensure you sanitize any sensitive information from your VSCode settings before committing. Review backup files for:

• Personal API keys or tokens
• Absolute file paths specific to your system
• Private configuration that shouldn't be shared

Cleanup

Backups are retained in git history. You can clean local backups using:

# Clean backups older than 30 days (commits changes)
make clean-old-backups

# Clean all backups (use with caution - commits changes)
make clean-all-backups

Note: Cleaning backups will create git commits to remove the files from version control.