Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate deployment of GitHub pages #3

Closed
wkillerud opened this issue Feb 26, 2018 · 6 comments
Closed

Automate deployment of GitHub pages #3

wkillerud opened this issue Feb 26, 2018 · 6 comments
Assignees
Labels
💻 technical Technical or infrastructure issue 💫 design system Design system meta

Comments

@wkillerud
Copy link
Contributor

The process of building the html documentation and pushing it to the gh-pages-branch needs to be automated. Preferably our CI should be setup to do this. Travis has a write up, that might help: https://docs.travis-ci.com/user/deployment/pages/

npm run build:htdocs builds the documentation, which ends up in dist.

@wkillerud wkillerud added the 💻 technical Technical or infrastructure issue label Feb 26, 2018
@selbekk selbekk added the 💫 design system Design system meta label Mar 6, 2018
@kwltrs
Copy link
Contributor

kwltrs commented Mar 9, 2018

@wkillerud You are currently the expert on travis. Do think using travis to push to gh-pages is a good idea?

@wkillerud
Copy link
Contributor Author

Sure, it looks like they have great support for this :) https://docs.travis-ci.com/user/deployment/pages/
I can set up a PR with a suggested config. We should consider which account we create the access token with though, perhaps it's time for a dedicated automation account.

@wkillerud
Copy link
Contributor Author

Solved by #78 and #89. Still TODO is to create a dedicated account and replace the GitHub token on Travis.

@wkillerud wkillerud assigned kwltrs and unassigned wkillerud Mar 13, 2018
@wkillerud
Copy link
Contributor Author

@kwltrs, can you sort out the dedicated account and new token? I can help with the config if you need :)

@selbekk
Copy link
Contributor

selbekk commented Mar 13, 2018

Should we close this issue and create a new one for creating a new dedicated account? This issue seems to be resolved.

@wkillerud
Copy link
Contributor Author

Created #96 to track the remaining work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 technical Technical or infrastructure issue 💫 design system Design system meta
Projects
None yet
Development

No branches or pull requests

3 participants