Sync with react.dev @ 5138e605 #1078
Closed
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
* Update meetups.md Added React Helsinki to meetups. * Update meetups.md
Co-authored-by: Ricky <[email protected]>
* Blog and docs: Sunsetting Create React App * fix link * tweaks * fix markdown * clarity + thanks
…te React App (Depreacted) page section (#7612)
* fix(docs): webpack branding states it should be lower case * chore: fix more occurrences --------- Co-authored-by: Strek <[email protected]>
* [Blog + Docs] Updates from feedback * Merge in changes from #7618 Co-authored-by: Mark Erikson <[email protected]> * Say the words "Vite", "Parcel", and "Rsbuild" * Tweaks from feedback * re-apply #7615 * merge in #7622 Co-authored-by: elitalpa <[email protected]> --------- Co-authored-by: Mark Erikson <[email protected]> Co-authored-by: elitalpa <[email protected]>
* Remove starting react project from setup page * Fix typo
fix 18.3.0 release changelog link
* Update nextjs link with the latest URL The previous link redirected users to a 404 page. * Update src/content/reference/react/useDeferredValue.md --------- Co-authored-by: Ricky <[email protected]>
* Update input.md Fix typo about input * Update src/content/reference/react-dom/components/input.md --------- Co-authored-by: Ricky <[email protected]>
* clarify alert message behavior in issue #7494 Reworded the explanation regarding the alert message in the documentation to better describe its behavior. The alert shows the previously entered name, with an initial value set to an empty string. * Update src/content/learn/state-a-components-memory.md * Update src/content/learn/state-a-components-memory.md --------- Co-authored-by: Ricky <[email protected]>
* Fix broken header link * Update sunsetting-create-react-app.md
…r <style> when using the `precedence` property (#7643)
This is the exact same fix as #6422 as the example is duplicated between the useOptimistic and <form> pages.
Ports over the fix in the facebook/react repo for this workflow. We don't have to wait for it to be labeled first, now that we have the reusable maintainer check.
Defaults permissions to none for all workflows, and only request extra permissions when needed. Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead.
* [ci] Fix permissions and don't use pull_request_target Defaults permissions to none for all workflows, and only request extra permissions when needed. Similar to facebook/react#32708, prefer the less permissive `pull_request` trigger instead. * [ci] Pin 3rd party actions to specific hash
facebook/react#32727 removes the `is_remote` param.
* Add React Prague community * Update link
* Remove captureOwnerStack canary banner * Update nav and site config
* update reactrouter url * Update src/content/learn/build-a-react-app-from-scratch.md --------- Co-authored-by: Ricky <[email protected]>
1. Stop using `canary` for `captureOwnerStack` sandboxes 1. Remove remaining Canary badges from `captureOwnerStack` mentions
Updated `react-ahmedabad` community link to respective domain name
Co-authored-by: Rick Hanlon <[email protected]>
… (#7682) * Fix small grammatical mistake * Update src/content/learn/reusing-logic-with-custom-hooks.md --------- Co-authored-by: Ricky <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Contributor
|
@jhonmike, gostaria de contribuir com o este projeto e tenho atuado na revisão de alguns PRs. Apesar de ter analisado ponto a ponto dos conflitos deste PR (commit pronto) não tenho permissão para subir aqui para análise e aprovação. Qual procedimento devo realizar para adquirir esta permissão? Faço essa chamada a você, pois vi PRs semelhantes com sua interação. Obrigada! |
Member
|
Olá @lanamesquita, obrigado por revisar os PRs, sempre que possível estou fazendo merge dos mesmo, esse que vem automático é um pouco mais chato e toda semana ele desatualiza. A sugestão é continuar revisando os demais PRs e quando quiser traduzir algo basta abrir um novo PR |
jhonmike
added
duplicate
Contributor
|
@jhonmike Então estes automáticos não valem a pena a revisão? Já tinha feito as alterações deste. Pois vi que tinham muitas alterações dos blocos de páginas, e o pt-br está mais distante da estrutura original. Se quiser posso te mandar por outro local para verificar. Nas revisões eu posso enviar um commit em vez de sugerir linha a linha? Vi que precisava ter permissão a mais para isto. Vou continuar nas revisões antes de entrar abrir novos PRs. Gostaria de ajudar na redução de PRs abertos. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
This PR was automatically generated.
Merge changes from react.dev at 5138e60
The following files have conflicts and may need new translations:
Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.
DO NOT SQUASH MERGE THIS PULL REQUEST!
Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.