You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pushing a pre-release branch, especially, is really helpful for contributors as it allows them to install their changes as an npm package (without releasing to npm)
Who needs to work on this
Developers, Tech writers?
Who needs to review this
Developers, Tech writers?
Done when
The content you are editing has changed. Please copy your edits and refresh the page.
romaricpascal
changed the title
Make sure documentation is up to date with new structure
Make sure GitHub documentation is up to date with new structure
May 15, 2023
romaricpascal
changed the title
Make sure GitHub documentation is up to date with new structure
Make sure docs is up to date with new structure
May 15, 2023
romaricpascal
changed the title
Make sure docs is up to date with new structure
Make sure the docs folder is up to date with new structure
May 15, 2023
Closed by #3975 (the PR was referencing the wrong issue). The docs have been reviewed, but we'll open issues should any problem arise when running our first pre-releases.
What
Check that the documentation inside the repository (in
docs
) are up to date with the new repository structure, especially:Why
We're making substantial changes to our repository structure ahead of v5. We need to ensure that our docs reflect these changes so they can help future us and contributors appropriately.
Pushing a pre-release branch, especially, is really helpful for contributors as it allows them to install their changes as an npm package (without releasing to npm)
Who needs to work on this
Developers, Tech writers?
Who needs to review this
Developers, Tech writers?
Done when
We've reviewed
The text was updated successfully, but these errors were encountered: