NuKeeper doesn't respect the targetBranch

[MartinDemberger]

🐛 Bug Report

I have a Azure Pipeline which starts NuKeeper on a release-Branch. The packages are determined for the master branch.

Hier is the console output.

Caching tool: nukeeper 0.34.0 x64
"C:\Program Files\dotnet\dotnet.exe" C:\hostedtoolcache\windows\nukeeper\0.34.0\x64\NuKeeper.dll repo D:\a\1\s *** --targetBranch origin/releases/_XXXXX_ -m 500 --change Patch -v d --consolidate --include _XXXXX_ --source _XXXXX_ --age 0 --label AutoCompleteWI --label Approve
Matched uri '_XXXXX_' to collaboration platform 'AzureDevOps'
FindPushFork. Fork Mode is SingleRepositoryOnly
2021-03-24T00:07:13Z: Started
GetGitRepositories: Requesting _XXXXX_/_apis/git/repositories?api-version=4.1
Using upstream fork as push, for project ePlato at _XXXXX_
User name missing from profile, falling back to .gitconfig
Git clone _XXXXX_, branch default, to C:\Users\VssAdministrator\AppData\Local\Temp\NuKeeper\repo-2c8d9d6cab7842508de68b3faaddf7aa
0 / 444715
44471 / 444715
88942 / 444715
133413 / 444715
177884 / 444715
222355 / 444715
266826 / 444715
311297 / 444715
311297 / 444715
355768 / 444715
400239 / 444715
444710 / 444715
Git clone complete
Found 936 packages

As you can see in the above output the parameter --targetBranch is set to origin/releases/_XXXXX_ but on clone default is used.

Expected behavior

The correct branch ist used for cloning.

Reproduction steps

Configuration

Version: 0.x.x

Platform if applicable:

• [ ] :hammer_and_wrench: NuKeeper CLI
• [ ] :sparkles: GitHub
• [X] :robot: AzureDevops
• [ ] :checkered_flag: Bitbucket
• [ ] :earth_americas: Gitlab
• [ ] :tv: Gitea
• [ ] :whale: Docker

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[MartinDemberger]

This isn't solved now but a PR is only a few clicks away ;-)