Improve error message when a tag is not found and match is set.

[jenshnielsen]

If match is set and you do not have any tags matching this but you do have other tags the error shown is git describe could not find a tag` which is slightly confusing since there are tags and running git describe at the command line will return a tag. This just tweaks the error message to include the match argument in such a case.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.67%. Comparing base (4d090c1) to head (20f6952).

❗ Current head 20f6952 differs from pull request most recent head d07ffbf. Consider uploading reports for the commit d07ffbf to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   97.67%   97.67%           
=======================================
  Files          17       17           
  Lines        1246     1249    +3     
  Branches      211      212    +1     
=======================================
+ Hits         1217     1220    +3     
  Misses         15       15           
  Partials       14       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jenshnielsen]

It was not obvious from a few mins of looking how to best update the test data depending on if match is used or not

[jwodder]

@jenshnielsen I've taken care of the tests, as well as various improvements to ensure that all mentions of git describe include not only --match but all other options passed as well.

[jenshnielsen]

Thanks @jwodder that looks like a great improvement and much more useful than my original contribution

[jwodder]

@jenshnielsen This has just been released in versioningit v3.1.0.