Docs: Transform all docs to the new structure & format #28242
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
cdedreuille
changed the title
☁️ Nx Cloud ReportCI is running/has finished running commands for commit a3269bb. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
- It previously mixed three package manager snippets with a common one, which doesn't work correctly
kylegach
changed the title
kylegach
added
documentation
ci:docs
* next: (26 commits) Use JS only story glob extension patterns in JavaScript projects Docs: Update Changelog by adding 7.6.x changes Telemetry: Detect Node version CLI: Improve error message when fetching CLI version empty the lock files use same version of yarn everywhere feat: migrate from pkg-dir feat: migrate from read-pkg-up Fix typo storyStoryV7 -> storyStoreV7. Update CHANGELOG.md for v8.1.10 [skip ci] Bump version from "8.2.0-alpha.9" to "8.2.0-alpha.10" [skip ci] Write changelog for 8.2.0-alpha.10 [skip ci] Addon-interactions: Fix deprecation warnings Allow esbuild version 0.21.x Bump version from "8.2.0-alpha.8" to "8.2.0-alpha.9" [skip ci] Update CHANGELOG.md for v8.1.9 [skip ci] Write changelog for 8.2.0-alpha.9 [skip ci] Addon-a11y: Workaround for Vite 5.3.0 compat fix the cra not being able to link by forcing resolutions remove packageManager field ...
kylegach
force-pushed
the
charles-transform-docs-next
branch
from
a3269bb to
44acc42
Compare
|
Not sure why Danger isn't running, but This was tested extensively during QA for the new docs site. No code review necessary (or even possible, really). |
4 tasks
58 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #
What I did
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:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake 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/coreteam 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>