-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
Describe the bug
entangled sync does not have a --force flag despite an error message being thrown
To Reproduce
$> entangled sync
[21:00:10] INFO Welcome to Entangled v2.4.2!
INFO Tangling.
INFO create `test.nix`
WARNING `test.nix` not managed by Entangled
ERROR conflicts found, breaking off (use `--force` to run anyway)
$> entangled sync --force
[20:59:57] INFO Welcome to Entangled v2.4.2!
Usage: entangled sync [OPTIONS]
Try 'entangled sync --help' for help
╭─ Error ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ No such option: --force │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Expected behavior
$> entangled sync
[21:00:10] INFO Welcome to Entangled v2.4.2!
INFO Tangling.
INFO create `test.nix`
WARNING `test.nix` not managed by Entangled
ERROR conflicts found, breaking off (use `--force` to run anyway)
$> entangled sync --force
[21:00:10] INFO Welcome to Entangled v2.4.2!
INFO Tangling.
INFO create `test.nix`
WARNING `test.nix` not managed by Entangled
WARNING conflicts found, but continuing anyway
Metadata
Metadata
Assignees
Labels
No labels