-
Notifications
You must be signed in to change notification settings - Fork 101
docs: Configure site to use Docusaurus shared components #2826
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
Draft
jessiemongeon1
wants to merge
40
commits into
main
Choose a base branch
from
docusaurus-shared-components
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
git-subtree-dir: docs/site/src/shared git-subtree-split: a12e42f47abe5ef999c396e381cb7662e925c01b
…us-shared-components
682f7bb0 Create README.md 2db79481 Initial shared components 2867701c Initial shared components 4cdbad24 Initial shared components 7807a109 Initial shared components b0df9e9f Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 682f7bb09a21f394c169597f24d1b92f441f1f68
Contributor
|
…us-shared-components
98a14614 Initial shared components 557e7735 Initial shared components 2a114abe Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 98a1461498a87b66d6f04434497e266698d992ce
…us-shared-components
32f64713 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 32f64713f6970edae583e3b8edad4d3484ffb4c5
…us-shared-components
79781d0b Initial shared components 127840e4 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 79781d0bf8957504596470160faf8a66073245a6
…us-shared-components
2c1b506f Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 2c1b506f6739d826892380fb1ae41822558595e1
241f0e88 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 241f0e88f17c915f812ad27fe9fff6130e53ac92
…us-shared-components
e8527622 Initial shared components 741f1a44 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: e8527622d2b0863a53b3b7e0e1ccb50b692bdc4f
63d80ad2 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 63d80ad2cfad6808b063bc7f283ce2cbb8853072
49c40299 Initial shared components git-subtree-dir: docs/site/src/shared git-subtree-split: 49c402990f405cf90076253fcbf9150b6577e3ff
…us-shared-components
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.
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)