docs: clarify scan vs fix workflow
This commit is contained in:
11
README.md
11
README.md
@@ -33,15 +33,15 @@ cargo install --path ./vid-repair
|
||||
### Common commands 💻
|
||||
|
||||
```bash
|
||||
# Scan files or folders
|
||||
# Most users: scan + fix in one step
|
||||
vid-repair fix /path/to/videos
|
||||
|
||||
# Scan only (no changes)
|
||||
vid-repair scan /path/to/videos
|
||||
|
||||
# Watch a folder and scan new/changed files once they finish writing
|
||||
vid-repair scan --watch /path/to/videos
|
||||
|
||||
# Fix (safe policy, in-place)
|
||||
vid-repair fix /path/to/videos
|
||||
|
||||
# Fix with aggressive policy (allows re-encode)
|
||||
vid-repair fix --policy aggressive /path/to/videos
|
||||
|
||||
@@ -49,6 +49,9 @@ vid-repair fix --policy aggressive /path/to/videos
|
||||
vid-repair scan --json /path/to/videos
|
||||
```
|
||||
|
||||
**Note:** `fix` always performs a full scan first, then repairs only if issues are found.
|
||||
Use `scan` when you just want a report without making changes.
|
||||
|
||||
### Scan depth 🔎
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user