Once file committed to repo and pulled from different client then file got corrupted.
We are keeping Excel files in Bitbucket managed repos without any problem, for several years.
Sounds like CRLF's in the files are getting converted into LF's by git. Normally git is good at detecting binary files that should never be touched, but for some reason here it sounds like git thinks your excel files are textual rather than binary.
More info here - images getting corrupt in this example, but essentially the same problem:
https://stackoverflow.com/questions/19411981/images-corrupt-after-git-push
Look at torek's comment there in particular:
Given 8950 4e47 0d0a 1a... vs 8950 4e47 0a1a it's immediately obvious (well... :-) ) that something thought this was a text file and turned CR-LF (0d0a) into LF-only (0a). Are you (or they) using the core.eol attribute and/or other git attributes to manage end-of-line normalization? – torek
8950 4e47 0d0a 1a...
8950 4e47 0a1a
0d0a
0a
core.eol
It looks like you're new here. Sign in or register to get started.