-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Auto deploy docs preview for every PR #5807
Comments
Maybe @sw-yx can help us out with this? |
hey! yea sure. really you just have to push this up on Netlify and its a button click away. do you want to do it on your own account? if i do it on mine i don't think i can transfer it over to you. just let me know when youve done it and i'll put you on the free OSS plan. |
That's something we need to figure out. Do we also need to install something in the GitHub repo so the link to the deploy appears on each PR? If so we'll need to ask @gaearon to do that. |
hmm. might need to install the Netlify Github app, yes. but it might already be installed since reactjs.org is on netlify. |
At the very least it will be easier to convince someone to install it if React is already using it. |
alright lets wait for Dan to see this. sounds like you do need an install |
I'll see if I can get this working with my fork of CRA and post some more specific instructions. |
@gaearon and @iansu apologies for the confusion. some setup was needed to deploy this monorepo/docusaurus setup. the best way to do this is with a netlify.toml configuration - in #5930 i have created a PR to set that up in CRA. You can see the result of this deploy here: https://trusting-lichterman-ee04c1.netlify.com
|
This is awesome. Thanks! 🎉 I think the What do we need to do to get this finished? I see that Dan has already merged your config PR. What else do you need from us? |
just need to proceed with the deploy :) You or Dan can do it since you should be on the "react team" within Netlify.
Once its deployed we can worry about naming. Do you want |
Deployed! I'm not sure about the domain name right now. I think we will continue using the GitHub pages URL until we come up with something better. This is a great start though. Now we can preview the docs when someone submits a PR. 🎉 |
Thanks for all your help @sw-yx! 😀 |
@sw-yx I'd like to change the name of our app to just |
yup on it. will take a while, i have to follow procedure with the squatter Update: squatter gave the ok. Should be released for you to claim by tomorrow |
* master: (39 commits) Added extension to .eslintrc (facebook#5988) Update links to docs in all package README files (facebook#5912) Use https for linked images in docs to fix mixed content warnings (facebook#5985) Improve error messaging in verifyPackageTree.js (facebook#5974) Add removeItem to localStorage mock in docs (facebook#5919) Add SASS_PATH instructions to Sass docs (facebook#5917) Suggest a different default for speed reasons (facebook#5959) Add pre-eject message about new features in v2 (facebook#5954) Add netlify.toml to prepare for deploy to netlify facebook#5807 (facebook#5930) Correct some comments (facebook#5927) Add note to docs about using Sass and Flow together (facebook#5823) Update PWA link in README (facebook#5907) Add placeholders to template README for bit.ly links. (facebook#5808) Disable copy to clipboard in cra --info (facebook#5905) Support setupTests.ts (facebook#5698) Remove unnecessary whitespace in template HTML Run prettier on HTML files (facebook#5839) Some Grammar fixes (facebook#5858) Fix link to page about running tests (facebook#5883) fix: make typescriptformatter support 0.5 of fork checker (facebook#5879) ...
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This is done! |
It would be nice to be able to see a preview of the docs when someone submits a change. We should be able to set that up using something like Netlify.
The text was updated successfully, but these errors were encountered: