fix problem with slash in branch name on Windows #295
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In 3d1b6f1 OS specific handling was added for line endings and path separators when executing Git commands.
This was over-generalizing the problem because the response of a Git command can also include a branch name and if that branch name would contain a slash (e.g. feature/my-feature) then this would be changed to a backslash on Windows which does not work.
I have removed the path separator handling from the Git command output and moved it instead to the changed file processing location.