semver init --force should not error if the .semver.yaml file isn't there.

[stewartbryson]

The --force option should work regardless of whether semver has been run previously:

❯ rm .semver.yaml

~
❯ semver init --force --release 1.2.3
Error: Config File ".semver" Not Found in "[/Users/stewartbryson]"
Usage:
  semver init [flags]

Examples:
semver init [--release v0.1.0] [--rc 1] [--beta 2] [--alpha 3] [--force]

Flags:
      --alpha int         current alpha version number
      --beta int          current beta version number
      --force             force recreate config file
  -h, --help              help for init
      --rc int            current rc version number
      --release version   release version (default v0.0.0-.0)

Config File ".semver" Not Found in "[/Users/stewartbryson]"

~
❯