Executing `np --version` tries to execute typical np executiion

Description

When executing np --version, it seems np is trying to actually run within current directory

The following example executes np --version in a directory which does not have .git initialized, when executing in a typical npm project, it has a different message

Steps to reproduce

1. In any directory, use np --version

Expected behavior

Show the current np version information

Environment

np - 7.3.0 (trying to upgrade to 7.4.0) Node.js - 14.5.0 npm - 7.0.15 Git - 2.30.0 OS - macOS 10.15.7

$ np --version        

✖ Could not infer the default Git branch. Please specify one with the --branch flag or with a np config.

or, from within a project which has a valid .git project

$ np --version      

Publish a new version of @codedungeon/gunner (current: 0.21.1)

? No commits found since previous release, continue? (y/N) 

[sindresorhus]

This is an intentional feature in meow: https://github.com/sindresorhus/meow/issues/113

It’s to make it possible for the auto-help thing to work in CLIs based on meow that have subcommand.

One way we could solve this is to allow --version, but only if there are no positional arguments. So np --yolo --version would be allowed, but np 1.2.3 --version would not. Still not sure it’s worth it though.

[sindresorhus]

Perhaps it would be a “feature” to meow in the future, but small use case at this point.

Feel free to open an issue on the meow repo.