5 ms·
This could make for some huge git repositories, storing largish binary files in git is a real trap for young players.
by justinjlynn 13y ago
This could make for some huge git repositories, storing largish binary files in git is a real trap for young players.
- glebm 13y agoRight, this could grow quickly over a few months at which point you would need to script filter-branch to rewrite older commits with spec/screenshots in a submodule.
- aiiane 13y agoIn general, filter-branch should be avoided rather than part of a long-term plan. It can cause all kinds of havoc as soon as you move beyond a handful of collaborators.
- deleted 13y ago[deleted]
- malandrew 13y agoI wonder if you could set up a parallel git-repo that is kept in sync when the master repo via scripting. This way you don't mix the work product that changed (code) and the results of those changes. (screenshots) Alternatively, it would be cool if you could keep a repo with copies of every working version of the end software product such as abinary file or live website. e.g. chrome checkout <commit-hash>