Misleading description of the --force switch (apply) and/or unexpected behavior

[x-yuri]

From the source code:

Set to 'true' to skip confirmation before applying changes. Set to 'conflict' to skip confirmation and overwrite existing resources

The way it works now...

Set to 'true' to skip confirmation to apply changes (if interactive). Set to 'conflict' to overwrite resources in case of a conflict

And if you specify --force conflict, you probably also want --force true, because... like, "ask me to apply changes, but overwrite if need be." Does it makes sense?

And in the previous repository it was !isForced && b.applyOpts.force != "conflict", but the tty logic was weird.