Change Details

Now, when new path is merged in WDQS GUI repo, we need to manually deploy it by doing: * `grunt deploy` in GUI directory of WDQS * Merge the resulting patch in `wikidata/query/gui-deploy` repo It'd be nice if these steps would be automatically executed post-merge by scripts, namely: * In post-merge step, run `grunt deploy` like script (better make different target so we can still deploy manually) * Commit the result to `wikidata/query/gui-deploy` * Move the gui submodule branch in `wikidata/querydeploy` to point to the new commit

Now, when new path is merged in WDQS GUI repo, we need to manually deploy it by doing: * `grunt deploy` in GUI directory of WDQS * Merge the resulting patch in `wikidata/query/gui-deploy` repo It'd be nice if these steps would be automatically executed post-merge by scripts, namely: * In post-merge step, run `grunt deploy` like script (better make different target so we can still deploy manually) * Commit the result to `wikidata/query/gui-deploy` * Move the gui submodule branch in `wikidata/query/gui-deploy` to point to the new commit

Now, when new path is merged in WDQS GUI repo, we need to manually deploy it by doing: * `grunt deploy` in GUI directory of WDQS * Merge the resulting patch in `wikidata/query/gui-deploy` repo It'd be nice if these steps would be automatically executed post-merge by scripts, namely: * In post-merge step, run `grunt deploy` like script (better make different target so we can still deploy manually) * Commit the result to `wikidata/query/gui-deploy` * Move the gui submodule branch in `wikidata/query/gui-deploy` to point to the new commit