How Saving Works
Source Files doesn't keep a clone. When a file is saved, from any app, it's committed straight to the repository's branch on the service as soon as the upload finishes.
That makes quick edits easy, but there's no staging area, no grouping of changes into one commit and no undo. For that, see When to Use Working Copy.
What each change commits
- Saving or duplicating a file makes one commit.
- A new folder gets an empty
.gitkeepfile, since Git can't store empty folders. - Deleting a folder makes one commit per file inside it.
- Moving or renaming makes two commits per file: one adding it at the new path and one removing the old one.
Commits are made as the account you signed in with, with the message set in Commit Messages. With Folder Sync, every file a sync uploads or deletes is a commit too.
Downloads and dates
Files download in full when you open them. On GitHub, Git LFS files download with their real contents, and everything shows the date of the branch's newest commit rather than of its own last change.
Large files and Git LFS
Source Files doesn't upload to Git LFS: saving a file kept in LFS commits the whole file into Git, so leave those to a Git client with LFS support. GitHub also refuses files of 100 MB or more.
A protected branch, a read-only repository or a file in .github/workflows can also make a save fail; Repository Problems has the fixes.