Closed olyism closed 4 years ago
Due to Github Page's limitation of only deploying to master
, this is my current resolution:
master
is for public files only. After the gh-pages
deployment script is run, the static files will override all files in master
development
is the main branchrelease/VERSION_NAME
, e.g. release/v1.4.2
.gitignore
ignores /public
folderdevelopment
branch, add git tag of the merge commitNote: this is the interim workflow whilst we're still using Github Pages. It seems like a good workflow, albeit cumbersome. We can look into a leaner process after we have another hosting environment.
Also, will need to fix the problem of Github Pages wiping out the custom domain setting.
Seems like the CNAME file must be in the root. See https://github.com/tschaub/gh-pages/issues/213
How might we create an efficient deployment workflow?
Current problems:
public/
folder is not ignoredrelease
branches, seems a bit cumbersomeSome initial ideas:
public/
folder