Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
stewartbryson opened this issue Jan 15, 2021 · 0 comments · Fixed by #9
Closed

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

stewartbryson opened this issue Jan 15, 2021 · 0 comments · Fixed by #9
Labels
bug Something isn't working

Comments

@stewartbryson
Copy link

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]"

~
❯
@maykonlf maykonlf added the bug Something isn't working label Sep 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants