Skip to content

Add the ability to not display Usage in case of errors not related to parameters #745

@dvilker

Description

@dvilker

Is your feature request related to a problem? Please describe.
For example, now, when I run changie batch auto, if there are no changes, I get:

Error: no unreleased changes found for automatic bumping
Usage:
  changie batch version|major|minor|patch|auto [flags]

Flags:
  -d, --dry-run              Print batched changes instead of writing to disk, does not delete fragments
      --footer-path string   Path to version footer file in unreleased directory
  -f, --force                Force a new version file even if one already exists
      --header-path string   Path to version header file in unreleased directory
  -h, --help                 help for batch
  -i, --include strings      Include extra directories to search for change files, relative to change directory
  -k, --keep                 Keep change fragments instead of deleting them
  -m, --metadata strings     Metadata values to append to version
      --move-dir string      Path to move unreleased changes
  -p, --prerelease strings   Prerelease values to append to version
  -j, --project string       Specify which project version we are batching
      --remove-prereleases   Remove existing prerelease versions

no unreleased changes found for automatic bumping

What's confusing is that it seems like the parameters are set incorrectly, not that there is a state error.

Describe the solution you'd like
Either remove Usage altogether in this case, or remove it if some parameter is present (--do-not-show-usage).

Describe alternatives you've considered
&2>/dev/null, but this looks strange, because another text error should also be sent to stderr (in stdout now).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions