I think that you can use a hook instead of sending the dist folder. Send the app folder and then you run your grunt task in a remote hook. You can read more about server side hooks here: http://git-scm.com/book/en/Customizing-Git-Git-Hooks#Server-Side-Hooks
William Seiti Mizuta @williammizuta Caelum | Ensino e Inovação www.caelum.com.br On Fri, Oct 11, 2013 at 12:03 AM, Stereokai <t...@stereokai.com> wrote: > I use one repo with develop and release branches for a Yeoman project. > > Simplified, my directory tree looks like this: > > root git directory > ├── app > └── dist (the build folder) > > > With Grunt.js I build my app straight into dist. > > I would like to use git subtree push --prefix dist origin release to > conveniently update release with a new build - as detailed in the Yeoman > documentation <http://yeoman.io/deployment.html>. > > Do I need to track, commit and push the dist directory in the developbranch > at all times to use this method? > > I would like to know as well - since on my own, I could not make the above > work conveniently - would a submodule tracking the release branch be a > better solution? > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
