3 ms·
If you are properly preparing your assets for web distribution you really don't want those files in a git repo. it messes up your commit history and doesn't pro
by sintaxi 10y ago
If you are properly preparing your assets for web distribution you really don't want those files in a git repo. it messes up your commit history and doesn't provide much value. I think gh-pages is fundamentally broken for this reason. IMHO its best to keep your source files in a git repo and publish your compiled assets to surge.
- wilg 10y agohttps://github.com/edgecase/middleman-gh-pages https://github.com/edgecase/middleman-gh-pages solves this problem by letting you do all your work on the master branch, then your build script compiles all your assets and commits them to the gh-pages branch, so it doesn't pollute your Git history.
- z3t4 10y agoIt's a common work-flow to have your stable/prod/dist/build in a separate branch, just like gh-pages is.