-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Docs: Test Coverage troubleshoot optimized builds #25278
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jonniebigodes
added
documentation
patch:yes
Bugfix & documentation PR that need to be picked to main branch
ci:docs
Run the CI jobs for documentation checks only.
labels
Dec 19, 2023
storybook-bot
pushed a commit
that referenced
this pull request
Dec 19, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
This was referenced Dec 19, 2023
Merged
storybook-bot
pushed a commit
that referenced
this pull request
Dec 20, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 21, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 22, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 22, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 22, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 24, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 28, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 29, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 29, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
storybook-bot
pushed a commit
that referenced
this pull request
Dec 29, 2023
Docs: Test Coverage troubleshoot optimized builds (cherry picked from commit 4495fa9)
github-actions
bot
added
the
patch:done
Patch/release PRs already cherry-picked to main/release branch
label
Jan 1, 2024
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ci:docs
Run the CI jobs for documentation checks only.
documentation
patch:done
Patch/release PRs already cherry-picked to main/release branch
patch:yes
Bugfix & documentation PR that need to be picked to main branch
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #25205
What I did
With this small pull request, the test coverage documentation was updated to factor in a small troubleshooting item to address the mentioned issue.
What was done:
Going to merge this as soon as the checklist clears to allow it to be available to be linked into a post incoming this week
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>