I saw that Drive supports file history and snapshots, and I'd like to understand how to use them in practice.
Say a project has copy, images, and page files. I only want to restore yesterday's version of the copy, while keeping the current images and pages. File history would be the right option rather than restoring a whole snapshot, correct?
Before asking the Agent to keep editing, do I need to explicitly tell it that I've just rolled the file back?
You are right to protect the current images and page files while recovering only the copy. The confusing part is the current Buda interface: Drive “History” mainly lists actions such as create, upload, rename, move and delete. It is not a per-file browser of old file contents with a Restore this version button. Where a Drive type supports snapshots, restoring one replaces the whole Drive state, not just a selected file; some cloud Drive types do not currently offer snapshot restore at all. Please do not try a whole-Drive restore on a live project just to recover copy.
If the copy lives in Git, find yesterday's commit, inspect the diff, and restore only that path into the current branch. If you have an independent old draft or backup, copy that single file to a new path, compare it, then replace the current copy after review. If your only possible source is a whole-Drive snapshot, preserve a complete copy of the current Drive first and plan recovery with someone who can verify the scope; do not experiment on the production Drive.
After a single-file rollback, tell the Agent which file changed and ask it to re-read the current file before continuing, rather than relying on text from its earlier Session. We have recorded per-file version viewing and restore, and the documentation needs to distinguish Drive storage types more clearly. Is this copy in a Git repo, or only in Drive? The Chinese discussion covers the same issue.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign inI saw that Drive supports file history and snapshots, and I'd like to understand how to use them in practice.
Say a project has copy, images, and page files. I only want to restore yesterday's version of the copy, while keeping the current images and pages. File history would be the right option rather than restoring a whole snapshot, correct?
Before asking the Agent to keep editing, do I need to explicitly tell it that I've just rolled the file back?
You are right to protect the current images and page files while recovering only the copy. The confusing part is the current Buda interface: Drive “History” mainly lists actions such as create, upload, rename, move and delete. It is not a per-file browser of old file contents with a Restore this version button. Where a Drive type supports snapshots, restoring one replaces the whole Drive state, not just a selected file; some cloud Drive types do not currently offer snapshot restore at all. Please do not try a whole-Drive restore on a live project just to recover copy.
If the copy lives in Git, find yesterday's commit, inspect the diff, and restore only that path into the current branch. If you have an independent old draft or backup, copy that single file to a new path, compare it, then replace the current copy after review. If your only possible source is a whole-Drive snapshot, preserve a complete copy of the current Drive first and plan recovery with someone who can verify the scope; do not experiment on the production Drive.
After a single-file rollback, tell the Agent which file changed and ask it to re-read the current file before continuing, rather than relying on text from its earlier Session. We have recorded per-file version viewing and restore, and the documentation needs to distinguish Drive storage types more clearly. Is this copy in a Git repo, or only in Drive? The Chinese discussion covers the same issue.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in