Closed dancingCamel closed 2 years ago
Sounds like a problem with file paths and the unix emulation git bash performs.
Sounds like a problem with file paths and the unix emulation git bash performs.
Yes, I think it's either the way git handles paths, or it's line endings. It's not exclusively git bash causing a problem - if a powershell script runs from inside a husky shell script, and when powershell runs on the pipeline we also get the same problem.
We use a library to interact with git. If this library and a specific shell don't work nicely together this should be fixed there.
Describe the bug Running dotnet stryker with a config file including "since":{"target":"master", "enabled":"true"} returns different numbers of files changed depending on the calling shell. Git BASH - every file in project appears as changed Windows Powershell - only changed files appear as changed cmd - only changed files appear as changed husky pre-push script calling powershell script which runs dotnet styker - every file in project appears as changed Powershell in Azure pipeline - every file in project apprears as changed.
Logs Powershell:
Git Bash:
Expected behavior Since target should only pick up the files that have actually been changed regardless of the calling environment
Desktop (please complete the following information):
Additional context husky pre-push script:
testrunner.ps1 (located in repo root):
stryker-config.json: