feature: Handling of tags and branches about giddyup HOT 3 CLOSED

"Giddyup could handle checking out and working with specific branches and tags"

Honestly, I'm not sure it can -- or at least, it doesn't make sense to.

Giddyup doesn't actually checkout or otherwise work with any references other than the SHA of the commit you give it. It has no concept of a branch to track, or anything of that nature. You could change it to do that, rather than work with the SHA directly, except that you'd have to use the post-update hook, which means you lose the ability to "reject" the commit if the deployment didn't happen (which means you need a dummy commit to actually make the deploy happen if it was a transient failure).

Sure, you could change the code slightly so that instead of rejecting a push to anything other than refs/heads/master, you can specify (via the config) a ref you must push to, but I'm really not sure what you gain from this -- you can easily teach git what to push to which remotes, so a git push staging, if your staging remote is configured correctly, should only push from the appropriate local branch to the master branch in the giddyup repo. If you've got people who'll accidentally type git push production instead of git push staging, then it's not such a stretch to assume they'll accidentally type git push production production instead of git push staging staging.

If you still think this is a good idea, I'll merge a patch that doesn't change default behaviour (should only be about 2 lines of code, plus some documentation), but I'm not going to implement it myself. Re-open if you put together a patch.

from giddyup.

Well, the main problem is that Giddyup forces me to use master branch, while it is quite common to build a project on different branches - i.e. for feature testing. Consider one repo, that has a master (production) and multiple feature branches. Now I want to deploy a devel. server for testing a specific feature. All activity is feature/foobar branch, and I'd like to push changes to my dev server...

Because master is hardcoded, giddup is useless in such scenario.

from giddyup.

git push dev feature/foobar:master

from giddyup.