When I get into github project page yet another time and switched view from master branch to development I came up with idea that we should change the default branch to development as we work with it more.<\/p>\n\n\n\n
So, I navigate to admin tab and changed default branch with confidence that I did something useful.<\/p>\n\n\n\n
On the other part of the project people found a typo in one of our front page and decided to hot fix it in production. They change 1 symbol and made the deployment. Checked that production is alive and went home. No body did precise checks as change was so minor.<\/p>\n\n\n\n
After the midnight we discover that there are to many errors coming in the log. And the issue was that development branch was deployed to production.<\/p>\n\n\n\n
At first sight it was complete magic, but after some investigation we found out the following.<\/p>\n\n\n\n
By changing the github default branch, you don’t just change the default branch shown in the web interface. The HEAD ref is set to that branch. When no branch is set on capistrano deploy script – it will checkout HEAD, not master. The only way how the github default branch could be implemented – was changing the HEAD ref. So lessons learned:<\/strong><\/p>\n\n\n\n When I get into github project page yet another time and switched view from master branch to development I came up with idea that we should change the default branch to development as we work with it more. So, I navigate to admin tab and changed default branch with confidence that I did something useful….<\/p>\n","protected":false},"author":15,"featured_media":7475,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Bogdan Gusiev"],"class_list":["post-215","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
Even that such behavior is non explicitly documented at help.github.com – clone function<\/a> and stated at this blog post<\/a>.<\/p>\n\n\n\n\n\n\n\n
From Capistrano recipe for git:<\/p>\n\n\n\n # When referencing \"head\", use the branch we want to deploy or, by # default, Git's reference of HEAD (the latest changeset in the default # branch, usually called \"master\"). def head variable(:branch) || 'HEAD' end <\/pre>\n\n\n\n
The structural way how capistrano without an explicit branch set would work – is using a HEAD ref, as master is just a convention (best practice).
When you think about it that way – it all makes sense. One thing led to another. No Magic.<\/p>\n\n\n\n