0182086350
Summary: I'm loving `react-native-git-upgrade`, such a life and time saver, but when doing the upgrade, if git hooks are defined globally to be applied, `react-native-git-upgrade` uses these git hooks, although they might not be relevant to the upgrade process (and potentially make it way longer). Btw, thanks ncuillery for the great tool 😄 To test, I : * cloned my project * upgraded it with the npm published `react-native-git-upgrade` version : Git hooks are running during the upgrade * cloned the `react-native` repo * did my modifications on the `react-native-git-upgrade/cliEntry.js` file * `npm i -g react-native-git-upgrade/` after running `yarn` in that folder * Re-cloned my project in another folder * Upgraded it with `react-native-git-upgrade` : The hooks are not running anymore, yay! [CLI] [ENHANCEMENT] [react-native/react-native-git-upgrade] - Do not run git hooks in the upgrade process I plan to add an option to the cli so you can pass `--verify` or `--use-git-hooks` if you DO want your git hooks to run, but don't have the time right now and I think the default should be to not run them. Closes https://github.com/facebook/react-native/pull/16855 Differential Revision: D6353781 Pulled By: hramos fbshipit-source-id: e4b0f55d10c37bc805b32cb4c0fe3c863346482d |
||
---|---|---|
.. | ||
README.md | ||
checks.js | ||
cli.js | ||
cliEntry.js | ||
index.js | ||
package.json | ||
yarn.js |
README.md
React Native Git Upgrade
This tool makes upgrading your apps to a new version of React Native easier than the stock react-native upgrade
command.
It uses Git under the hood to automatically resolve merge conflicts in project templates (native iOS and Android files, .flowconfig
etc.). These conflicts happen when a new React Native version introduces changes to those files and you have local changes in those files too, which is quite common.
Usage
See the Upgrading docs on the React Native website.
Basic usage:
$ npm install -g react-native-git-upgrade
$ cd MyReactNativeApp
$ react-native-git-upgrade