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.

Sign up for GitHub

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

Jump to bottom

Provide Storybook deployment #116

Closed
1 of 5 tasks
jeremylenz opened this issue Jan 14, 2020 · 1 comment
Closed
1 of 5 tasks

Provide Storybook deployment #116

jeremylenz opened this issue Jan 14, 2020 · 1 comment

Comments

@jeremylenz
Copy link
Contributor

I'm submitting a…

  • Regression (a behavior that used to work and stopped working in a new release)
  • Bug report
  • Feature request
  • Documentation issue or request
  • Support request

Expected Behavior

The goal is to allow foreman and plugins to deploy their stories to a remote server so they can share the URL with others.

Manual Operations

Consumers would like to run a command manually that will deploy their stories.

Automations

  1. When the master branch gets updated, deploy the master stories
  2. When someone opens/updates a PR, deploy the PR to a temporary remote and comment on the PR with the story-url.

Current Behavior

The Storybook is not deployed and the only way to see it is npm run stories. As a result, many devs don't know of the existence of our Storybook.

Possible Solution

Remote Options

  • gh-pages
  • surge.sh
@jeremylenz
Copy link
Contributor Author

closing, Storybook is deployed at https://foreman-storybook.surge.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremylenz