It is possible to not add configuration files for GitVersion when creating a module using the templates. But if GitVersion is installed it will be used regardless.
Verbose logs
n/a
How to reproduce
Created a module using a template and skip adding GItVersion configuration.
Expected behavior
Not to use GitVersion if configuration is not available.
Current behavior
Always uses GitVersion if installed.
Suggested solution
Maybe we could make it so that the task only tries GitVersion if the file Gitversion.yml is present.
Operating system the target node is running
n/a
PowerShell version and build the target node is running
Problem description
It is possible to not add configuration files for GitVersion when creating a module using the templates. But if GitVersion is installed it will be used regardless.
Verbose logs
How to reproduce
Created a module using a template and skip adding GItVersion configuration.
Expected behavior
Not to use GitVersion if configuration is not available.
Current behavior
Always uses GitVersion if installed.
Suggested solution
Maybe we could make it so that the task only tries GitVersion if the file
Gitversion.ymlis present.Operating system the target node is running
PowerShell version and build the target node is running
Module version used