The upload replaces every file in the remote Apps Script project
Source references: 3This is not an incremental sync: the documentation states that it replaces all project files. If --dir is omitted, it also selects files from the current directory, so a wrong directory, project ID, or incomplete source tree can overwrite the correct version. Confirmation reduces accidental execution but does not validate content or provide rollback.
Existing code, HTML, and manifests in the target Apps Script project may be removed or replaced, potentially breaking deployments and automations or causing hard-to-recover code loss.
This is a credible risk to the user's project files. The command writes a local directory to the specified Apps Script project and explicitly replaces every file; if `--dir` is omitted, it uses the current directory. A wrong project ID, wrong directory, or incomplete local file set could therefore overwrite valid remote content. The required user confirmation reduces accidental use but does not remove the replacement behavior. The user can ask whether preview, remote backup, or recovery is available and restrict execution to a verified project ID and directory.
|------|----------|---------|-------------|| `--script` | ✓ | — | Script Project ID || `--dir` | — | — | Directory containing script files (defaults to current dir) |Show 2 other places
- Skips hidden files and node_modules automatically.- This replaces ALL files in the project.> [!CAUTION]> This is a **write** command — confirm with the user before executing.