Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE]: /diag and /nonormalize are mutually exclusive #4395

Open
2 tasks done
trondhindenes opened this issue Jan 27, 2025 · 1 comment
Open
2 tasks done

[ISSUE]: /diag and /nonormalize are mutually exclusive #4395

trondhindenes opened this issue Jan 27, 2025 · 1 comment

Comments

@trondhindenes
Copy link

Prerequisites

  • I have written a descriptive issue title
  • I have searched issues to ensure it has not already been reported

GitVersion package

GitVersion.Tool

GitVersion version

6.1.0

Operating system

Linux

What are you seeing?

When running dotnet-gitversion /config <config-file> /diag /nonormalize, diagnostics output is excluded.

What is expected?

Diagnostics output should always be included regardless of other "non-output-related" parameters passed.

Steps to Reproduce

See "What are you seeing?" for repro

RepositoryFixture Test

No response

Output log or link to your CI build (if appropriate).

@trondhindenes trondhindenes changed the title [ISSUE]: /diag and /nonormalize are mutualliuy exclusive [ISSUE]: /diag and /nonormalize are mutually exclusive Jan 27, 2025
@HHobeck
Copy link
Contributor

HHobeck commented Jan 29, 2025

@trondhindenes: I invite you to create a pull-request to fix the usage of /diag and /nonormalize option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants