> Does this not do what you want?

That wasn't updating to the current master of qless-core.  I couldn't figure out why.  I don't really know how to use submodules.  I dislike them like most people who have ever used them.  This was the only way I could figure out how to consistently get this to pull down the latest qless-core.

> Doing git reset --hard origin/master programmatically is almost certainly a bad idea. Phil had something similar in a build script for one of the Meerkat repos and this actually caused me to lose some code that I was working on.

If you can tell me how to get the submodule to always update to the latest qless-core HEAD, I'm happy to switch to whatever way is better.  `git submodule update` wasn't working for me.

Note also that this task will _never_ run `reset --hard` on the qless repo; only on the qless-core repo.  Also, it only happens when you manually invoke the `core:update` task, which, by its very name, implies it's going to update to the latest qless-core.