Documentation about how to juggle the git-repos when developing in the different components.
I think we should let ggpyjobs track upstream branch of sc2reader instead of a specific commit, so people can pull down updates automatically.
I'm also planning to remove the ggpyjobs component in the root of the stack, since it's perfectly possible to work directly in /vagrant/esdb/vendor/ggpyjobs on the stack.
Documentation about how to juggle the git-repos when developing in the different components.
I think we should let ggpyjobs track
upstream
branch ofsc2reader
instead of a specific commit, so people can pull down updates automatically.I'm also planning to remove the ggpyjobs component in the root of the stack, since it's perfectly possible to work directly in
/vagrant/esdb/vendor/ggpyjobs
on the stack.Let me know what you think.