Holy crap. Why is the Rakefile so... weird?
Anyway, the current deploy process is this:
- Remove all files from
_deploy (minus the .git folder)
- Copy generated files from
jekyll build from public to _deploy
cd _deploy && git add . && git commit -m {message} && git push
This seems all fine and dandy until you realize that _deploy needs to be it's own git repo. This means that the current setup process is to rm _deploy && git clone [ufsit.github.io repo] _deploy which is pretty silly in my opinion.
Following #3, the Rakefile should be updated to allow for an easier set up. #3 might solve this issue, but it might not. We'll see.
Holy crap. Why is the Rakefile so... weird?
Anyway, the current deploy process is this:
_deploy(minus the.gitfolder)jekyll buildfrompublicto_deploycd _deploy && git add . && git commit -m {message} && git pushThis seems all fine and dandy until you realize that
_deployneeds to be it's own git repo. This means that the current setup process is torm _deploy && git clone [ufsit.github.io repo] _deploywhich is pretty silly in my opinion.Following #3, the Rakefile should be updated to allow for an easier set up. #3 might solve this issue, but it might not. We'll see.