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

The magical ability to only run storyshots that might have changed #12

Open
Auroratide opened this issue Jul 13, 2023 · 0 comments
Open

The magical ability to only run storyshots that might have changed #12

Auroratide opened this issue Jul 13, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Auroratide
Copy link
Collaborator

When a repo gets to 200+ storybooks, it takes upwards of several minutes to run all the storyshots.

It would be cool if there was somehow a way to detect which storyshots can't have changed (because their code and the code they depend on hasn't changed) and therefore not run those by default.

We'd still want to maintain the ability to run all of them, for instance on the pipeline.
@Auroratide Auroratide added the enhancement New feature or request label Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Auroratide