for this to work the branch name has to be 'sane' - it should easily translate into valid filenames/ directory names. We currently match against ^[a-zA-Z0-9/-]+$, so
not sane: (detached in 23497sdjkf2345dgfb), me so krazy, feature/:love:
not sane branches get deployed in build/branches/branch-name-too-weird-so-we-took-this-for-a-name
a deploy-gh-pages will do the same as install, will also add/ commit/ push to gh-pages
Note on travis
travis (and probably other CI providers) will use a detached branch. It's doing a git checkout -qf {{commit-hash}} to be sure it's running against the correct commit. As a consequence
the branch name looks like (detached in {{commit-hash}}
the branch name is not 'sane'
installation will commence in the build/branches/branch-name-too-weird-so-we-took-this-for-a-name folder
(pushing to gh-pages from travis will need some work anyway ...)
Local feature branch deployments
buildbuild/branches/{{branch_name}}. This means the branch will be available on https://sverweij.github.io/mscgen_js/branches/{{branch_name}}^[a-zA-Z0-9/-]+$, sothis-is-a-branch-yo,feature/Houd-je-bek,hotffix/oops_hope_nobody_sees_this123(detached in 23497sdjkf2345dgfb),me so krazy,feature/:love:build/branches/branch-name-too-weird-so-we-took-this-for-a-nameNote on travis
travis (and probably other CI providers) will use a detached branch. It's doing a
git checkout -qf {{commit-hash}}to be sure it's running against the correct commit. As a consequence(detached in {{commit-hash}}build/branches/branch-name-too-weird-so-we-took-this-for-a-namefolder(pushing to gh-pages from travis will need some work anyway ...)