feat: support regex tag exclusions

[arturcic]

Description

Adds ignore.tags, a sequence of regular expressions for excluding tags from version-source discovery.

• Matches case-insensitively against the friendly tag name without refs/tags/.
• Uses OR semantics when multiple expressions are configured.
• Rejects invalid expressions during configuration validation.
• Keeps the tagged commit itself eligible for version calculation.
• Includes configuration parsing, builder, cache isolation, public API, schema, workflow snapshot, documentation, and integration coverage.

Related issue

Part of #5130.

Stack

1. #5151 - order configuration properties alphabetically
2. This PR - ignore tags
3. #5148 - ignore branches

Depends-On: #5151

Validation

• GitVersion.Configuration.Tests: 107 passed.
• Focused GitVersion.Core.Tests with LibGit2Sharp: 7 passed.
• Focused GitVersion.Core.Tests with managed Git: 7 passed.
• BuildPrepare completed successfully with zero warnings and errors.
• dotnet format src/GitVersion.slnx --no-restore completed successfully.
• Regenerated only schemas/7.0/GitVersion.configuration.json.

Checklist

• Code follows the project style.
• Documentation is updated.
• Tests cover the change.
• New and existing affected tests pass.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Pull request overview

Copilot reviewed 20 out of 20 changed files in this pull request and generated no new comments.

[arturcic]

Hi @HHobeck, could you please take a look at this PR when you have a chance? Thank you!

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 ⛓️ Depends-On Requirements

Requirement based on the presence of Depends-On in the body of the pull request

• depends-on = GitTools/GitVersion#5151 [⛓️ Order configuration properties alphabetically #5151]

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[HHobeck]

I need some time for the review. Anyway, what I was thinking about: Could we make case-insensitivity optional? Users who need it can easily add the modifier inline themselves, for example: (?i)^experimental-

[arturcic]

Thanks for raising this. GitVersion currently compiles configuration-supplied regexes through the shared RegexPatterns.Cache, which applies RegexOptions.IgnoreCase. This includes branch regexes, tag-prefix, version-in-branch patterns, bump-message patterns, custom merge-message formats, and ignore.paths.

I’d therefore prefer to keep ignore.branches and ignore.tags case-insensitive by default for consistency with the existing configuration behavior.

Users who need case-sensitive matching can disable case-insensitive matching inline with (?-i), for example:

ignore:
  tags:
    - '(?-i)^experimental-'\n```\n\nThis matches `experimental-...` but not `Experimental-...`.

[HHobeck]

Thanks for raising this. GitVersion currently compiles configuration-supplied regexes through the shared RegexPatterns.Cache, which applies RegexOptions.IgnoreCase. This includes branch regexes, tag-prefix, version-in-branch patterns, bump-message patterns, custom merge-message formats, and ignore.paths.

I’d therefore prefer to keep ignore.branches and ignore.tags case-insensitive by default for consistency with the existing configuration behavior.

Users who need case-sensitive matching can disable case-insensitive matching inline with (?-i), for example:

ignore:
  tags:
    - '(?-i)^experimental-'\n```\n\nThis matches `experimental-...` but not `Experimental-...`.

Hmm okay. Can you document it? Fair enough if we want to have the behavior to be case insensitive. But why we have for example this in our configuration?

tag-prefix: "[vV]?"
version-in-branch-pattern: "(?<version>[vV]?\\d+(\\.\\d+)?(\\.\\d+)?).*"

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[arturcic]

Hmm okay. Can you document it?

@HHobeck Documented in a1c81bc: the reference now explains the case-insensitive default and (?-i) opt-out, and every regex-specific schema description includes the same guidance. The [vV] defaults are redundant under the current behavior, so I left them unchanged as unrelated cleanup.

[arturcic]

Hi @HHobeck, when you have a chance, could you please take another look at the updated PR? Your review feedback has been addressed. Thank you!

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[mergify]

Thank you @arturcic for your contribution!