It is not recommended to store large binaries into git.
Because git is architectured to store every version of every file, everytime you push a new large binary, you simply increase the size of the repository for the same amount.
Currently, this repository is already larger than 200MB compressed.
It is recommended to always push source files, and let every developer being able to recreate binaries from his disk, or during a specific build process.
My suggestion here is to remove (and add to .gitignore) all help related files.
[ ] remove and ignore the .chm file (66MB)
[ ] remove the output/ directory and add to .gitignore
I need your confirmation and advice about what could be removed and added to .gitignore: that the chm can be generated from the sandcastle project in visual studio, and that the Help/Output/ directory can be generated from docfx ?
After that, I will try to find a way to also remove these binaries from the git history, so the project size could be reduced.
tbolon
commented
4 years ago
It is not recommended to store large binaries into git.
Because git is architectured to store every version of every file, everytime you push a new large binary, you simply increase the size of the repository for the same amount.
Currently, this repository is already larger than 200MB compressed.
It is recommended to always push source files, and let every developer being able to recreate binaries from his disk, or during a specific build process.
My suggestion here is to remove (and add to .gitignore) all help related files.
I need your confirmation and advice about what could be removed and added to .gitignore: that the chm can be generated from the sandcastle project in visual studio, and that the Help/Output/ directory can be generated from docfx ?
After that, I will try to find a way to also remove these binaries from the git history, so the project size could be reduced.