Repository navigation
docs: update stale facebook/react-native links in package READMEs - #59458
saiyam-jain-dev wants to merge 1 commit into
Conversation
The repo moved from github.com/facebook/react-native to github.com/react/react-native. The package.json files in these packages already reference the new URL, but the READMEs still link to the old org. Update them for consistency. Affected packages: - @react-native/eslint-plugin: link to eslint-config-react-native - @react-native/dev-middleware: link to community-cli-plugin
|
Hi @saiyam-jain-dev! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Summary
Two package READMEs still link to \github.com/facebook/react-native\ while their own \package.json\ files already reference \github.com/react/react-native. This makes the READMEs consistent with their package metadata.
Packages updated:
Historical issue links, version-pinned links, and clone URLs were intentionally left unchanged.
Test Plan
Documentation-only change. No behavior change.
Changelog
[INTERNAL] [CHANGED] - Update stale github.com/facebook/react-native links to github.com/react/react-native in eslint-plugin and dev-middleware READMEs