Git and project files

Keep a normal local Git checkout for commits, branches, and remotes. Use a FlashDrive drive for the project files you want your team or agents to read and work on.

Upload a selected project snapshot

In your local checkout, select the branch and review the files you intend to share:

git status --short
git switch BRANCH
git status --short

Upload the selected source paths to your drive:

flashdrive --drive DRIVE_ID upload ./src ./README.md --recursive --dry-run
flashdrive --drive DRIVE_ID upload ./src ./README.md --recursive --wait

Review the dry run first. Select source files explicitly and keep credentials, dependency directories, and generated output local. Check the upload result before using the drive copy.

Work on project files through a mount

Mount the drive to edit its files with your usual programs. Use a separate project drive for organization. Restrict access through workspace membership and connection grants; a separate drive alone does not make files private. Folders inside a drive do not create separate permissions.

Saving a mounted file updates shared drive content after synchronization. A repository inside a mount keeps its .git directory on the controlling machine. Other machines share the working files, not Git history. A drive save does not create a commit, push, or remote CI job.

Only initialize or clone a repository when the user requests it, in a new or empty folder. If another machine reports “not a git repository,” do not run git init to repair it. Taking over Git requires the user to approve the consequences: the new machine can rewrite shared files, and a new repository does not contain the old history. The CLI’s --take-over-git and --release-git controls must be deliberate, not automatic recovery steps. See the current Git, takeover, and recovery guidance before using them.

Branch switches, pulls, merges, rebases, resets, and cleans can rewrite or delete files for everyone sharing the mount. Review changes and ask before those operations. Never confirm unexpected removals. Preserve local Git history, drafts, and conflict copies until recovery is complete.

Review an agent’s changes

Read or download the changed files, compare them with your checkout, and apply the changes you intend to keep. For one file:

mkdir -p ./review
flashdrive file get FILE_ID ./review/handbook.txt
git diff --no-index -- handbook.txt ./review/handbook.txt

The downloaded copy is for review. This command compares the two files without applying changes; exit status 1 means they differ. Compare and apply the changes you intend before replacing the tracked file or committing. Keep conflict copies until their changes have been reconciled.

Use your existing Git remote and CI setup for reproducible builds. Before a runner exits, confirm uploads finished or unmount successfully so pending local changes are not lost with an ephemeral machine.