Nevermind those branch names, thatâs just the way the deploy resource works and I guess it has to do with the shallow clone it uses. In Git, branches are no more than âflagsâ, or âtagsâ, or âaliasesâ that point to a specific node (a commit, in this case) of the acyclic graph thatâs the commit tree. Each commit has a unique revision ID thatâs a hash of all of itself plus its parent(s), forming a graph. The deploy_revision resource deploys the code in a releases/<commit_ID> directory, relative to the deploy root. Check that ID and see if it matches with the most current commit ID of your âdevelopmentâ branch. If it does, youâre good. I find this 2010 OSDC talk very explanative and easy to follow if youâre interested in the way Git manages commits, branches, tags, etc: http://2010.osdc.com.au/proposal/196/git-ages-4-and â it certainly opened my eyes when I was beginning to learn it. -- Cassiano Lealhttp://cassianoleal.com http://twitter.com/cassianoleal On July 18, 2013 at 22:29:24, Liam Kirsher ( ) wrote:
|
Archive powered by MHonArc 2.6.16.