Improve docs re. git.tagMatch

Author: webpro

docs/git.md

@@ -46,11 +46,15 @@ Example: `--git.tagName=${name}@${version}`
 ## Tag Match
 
 Use `git.tagMatch` to override the normal matching behavior to find the latest tag. For instance, when doing a major
-release to find and set the latest major tag, and include all commits in the changelog since this matching tag.
+release to find and set the latest major tag, and include all commits in the changelog since this matching tag. Note
+that this represents a glob (not a regex):
 
-Example: `git.tagMatch: "[0-9]+\\.[0-9]+\\.[0-9]+"`
+Example: `git.tagMatch: "[0-9]*\.[0-9]*\.[0-9]*"`
 
-This can be useful when using a plugin to determine the next tag:
+Or only `"[!-]*"`, as this would match everything that excludes a hyphen, which is normally used excusively in
+pre-releaseses.
+
+This could also be useful when using a plugin to determine the next tag:
 
 Example: `git.tagMatch: "[0-9][0-9].[0-1][0-9].[0-9]*"`
 

docs/pre-releases.md

@@ -46,7 +46,7 @@ release-it major
 When all commits since the latest major tag should be added to the changelog, use `--git.tagMatch`:
 
 ```bash
-release-it major --git.tagMatch='[0-9]+\\.[0-9]+\\.[0-9]+'
+release-it major --git.tagMatch='[0-9]*\\.[0-9]*\\.[0-9]*'
 ```
 
 This will find the latest major matching tag, skipping the pre-release tags.