-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Convert from docusaurus to nextra #4240
Conversation
Hi @JoviDeCroock, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
c32daa0
to
cc1aed1
Compare
f952870
to
ee4e1df
Compare
ee4e1df
to
9c7d615
Compare
Sounds fine, ideally, we wouldn’t need to do that but we can always try to fix it later |
|
9c7d615
to
27892ff
Compare
@yaacovCR I think I found what could have been causing the issue for you 😅 I purposefully didn't add the new content yet to make the PR easier to review, currently it's basically a copy of the content within graphql.org and moving the website to its own lockfile. Regarding typedoc, I am personally not a big fan as TypeScript provides more value here. |
7bc980b
to
31e2ed2
Compare
2c2117b
to
a120b3f
Compare
Co-authored-by: Yaacov Rydzinski <yaacovCR@gmail.com>
a120b3f
to
99776c3
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This converts the existing docusaurus website to nextra just like https://github.com/graphql/graphql.github.io. This is a first step in moving the documentation here and having a redirect from graphql.org to graphql-js.org. Not sure yet why codecov started failing 😅 when I run `testonly:cover` locally it tells me we are 100% covered. WDYT about isolating the dependencies for the website in that folder? As seen in graphql@9c7d615 this prevents the weird CI leaks that we're seeing Resolves graphql#4200 --------- Co-authored-by: Yaacov Rydzinski <yaacovCR@gmail.com>
This converts the existing website to nextra just like https://github.com/graphql/graphql.github.io. This is a first step in moving the documentation here and having a redirect from graphql.org to graphql-js.org. Not sure yet why codecov started failing 😅 when I run `testonly:cover` locally it tells me we are 100% covered. WDYT about isolating the dependencies for the website in that folder? As seen in graphql@9c7d615 this prevents the weird CI leaks that we're seeing Resolves graphql#4200 --------- Co-authored-by: Yaacov Rydzinski <yaacovCR@gmail.com>
This converts the existing website to nextra just like https://github.com/graphql/graphql.github.io. This is a first step in moving the documentation here and having a redirect from graphql.org to graphql-js.org. Not sure yet why codecov started failing 😅 when I run `testonly:cover` locally it tells me we are 100% covered. WDYT about isolating the dependencies for the website in that folder? As seen in graphql@9c7d615 this prevents the weird CI leaks that we're seeing Resolves graphql#4200 --------- Co-authored-by: Yaacov Rydzinski <yaacovCR@gmail.com>
This converts the existing website to nextra just like https://github.com/graphql/graphql.github.io. This is a first step in moving the documentation here and having a redirect from graphql.org to graphql-js.org. Not sure yet why codecov started failing 😅 when I run `testonly:cover` locally it tells me we are 100% covered. WDYT about isolating the dependencies for the website in that folder? As seen in graphql@9c7d615 this prevents the weird CI leaks that we're seeing Resolves graphql#4200 --------- Co-authored-by: Yaacov Rydzinski <yaacovCR@gmail.com>
This converts the existing docusaurus website to nextra just like https://github.com/graphql/graphql.github.io. This is a first step in moving the documentation here and having a redirect from graphql.org to graphql-js.org.
Not sure yet why codecov started failing 😅 when I run
testonly:cover
locally it tells me we are 100% covered.WDYT about isolating the dependencies for the website in that folder? As seen in 9c7d615 this prevents the weird CI leaks that we're seeing
Resolves #4200