Conversation
|
If I understand it right, after this change pushing to master will auto-deploy the storybook documentation site. Since the gh-page is the API documentation for the npm package, would it make sense to only/always update it when the npm package is published? Is it possible to trigger a git workflow based on pushing a new tag that matches a pattern, like |
|
It would be cool to auto-incrementing the version and npm publish on every push to master by default, but then we'd need to select major/minor/patch on every push to master. (There was an npm package we looked at that did this, iirc.) |
|
@pixelbandito Both of those suggestions are fantastic. And yes, they are both attainable. I figured until we could put that setup together, it would be worth having the documentation updates automatically and we could drop the need for the dev dependency altogether. In any case, I'd like to get this in for now and revisit that flow on Monday now that we have a CI/CD pipeline we can use. |
Uses a pre-built Github Workflow action to deploy our GitHub pages documentation.