You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 21, 2021. It is now read-only.
I would like to manage the deployment automatically. Whether that goes through a Heroku pipeline or a CI service like TravisCI isn't as important. I just want the site to get deployed from the latest master (or maybe another branch like release).
Given our current setup (see #111), there would be two parts to this although they aren't equally important.
Firstly, we could have TravisCI write to the gh-pages branch (which github pages uses). This would solve the vast majority of the deployment headaches.
I would like to manage the deployment automatically. Whether that goes through a Heroku pipeline or a CI service like TravisCI isn't as important. I just want the site to get deployed from the latest master (or maybe another branch like
release
).Given our current setup (see #111), there would be two parts to this although they aren't equally important.
gh-pages
branch (which github pages uses). This would solve the vast majority of the deployment headaches.The text was updated successfully, but these errors were encountered: