Thanks for the quick response, Marc. It's a bug, not in your product, but in Windows git itself, as this is where the perceived needed changes are being pushed from.

I mention this issue as Atlassian Sourcetree folks (properly) noted that this is git behavior, and passed on a method to resolve this issue. If you folks had a workaround in mind for this kind of potential problem, you'd have a leg up on them.

(I understand this is an issue with git itself, but a way to detect these issues outside of git might have wider implications)