-
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
graphql-js.org is only partially deprecated #4200
Comments
This was referenced Oct 15, 2024
JoviDeCroock
added a commit
that referenced
this issue
Oct 20, 2024
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 --------- Co-authored-by: Yaacov Rydzinski <[email protected]>
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this issue
Nov 26, 2024
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 <[email protected]>
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this issue
Dec 3, 2024
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 <[email protected]>
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this issue
Dec 3, 2024
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 <[email protected]>
yaacovCR
added a commit
to yaacovCR/graphql-js
that referenced
this issue
Dec 3, 2024
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 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like graphql-js.org has been deprecated in favor of graphql.org/graphql-js. Our README even points to graphql.org/graphql-js.
So we really should:
I am not in a position to do 2, but have submitted a PR doing 1, and once 2 is done, I can do 3.
The text was updated successfully, but these errors were encountered: