Yeah... the tagged branch was actually the (remote) master one... and fully pushed.
Oh well. An own branch (e.g. production) which I update from the master one on specific occasions works instead of tags, so that's fine for me, too... but it according to the documentation and after having a quick glimpse into the code it 'should' work with tags, too... That's why I was a little bit confused here. Cheers, -J On Jan 18, 8:59 pm, "Mislav Marohnić" <[email protected]> wrote: > 2009/1/18 Jörg Battermann <[email protected]> > > > > > Hello Mislav, > > > yep... just double checked: > > > macPro:dw.se-backend joerg$ git push --tags > > Everything up-to-date > > Well, my suggestion was stupid because you don't need to push tags to deploy > a tag. Capistrano resolves branch/tag names *locally* on your machine and > later uses the raw SHA1 in the deployment process. You have to make sure > that the branch this commit is part of is pushed to your repo. > > If it is, and apparently you've made sure it's fine, I can't really tell > what's the problem. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
