[Bug] Cannot use output parameter due to it being hardcoded by task

Moved from https://github.com/GitTools/GitVersion/issues/2473

Describe the bug Running gitversion with /output file parameter gets overwritten. Actually it gets overwritten twice with two different parameters - json and buildserver.

C:\hostedtoolcache\windows\GitVersion.Tool\5.5.1\x64\dotnet-gitversion.exe D:/a/1/s /output json /output buildserver /config /output file

Expected Behavior

Being able to specify intended output, perhaps as parameter

Actual Behavior

buildserver output type gets precedence over both json and file outputs

Possible Fix

Expose output as parameter

Steps to Reproduce

Create task that will save GitVersion.json file using /output file parameter

Context

I’m not able to create json artifact to reuse it in other jobs

[chris-codeflow]

Hello @quasarea. I forgot to say thanks for the info on the default file name (GitVersion.json).

[chris-codeflow]

Hello @quasarea. I just ran a GitHub actions test to verify the above. It all worked as expected (it created output variables in JSON format, it created outputs for the GitHub build agent and it output the version variables to a specified file, which I proved by displaying the contents of the file in a separate step.

Snippet from action:

- name: Output version to file
  uses: gittools/actions/gitversion/execute@v0.9.8
  with:
    additionalArguments: '/output file /outputfile ./SemVer.json'

- name: Display version from file
  run: |
    cat ./SemVer.json

See GitHub workflow file for full details.