Pavlos Vinieratos

also, something to note.. github issues can have multiple templates. github pull requests cant. its one template for PRs and that's it. Are we ok with the way these files...

First, awesome suggestion, Let's do it! > 2. Create a branch (e.g. 0.62.0-rc.5) and push it (should be done on top of the last release branch); I wouldn't put it...

Closing this. We have that and it's working.

seems like the issue is fixed in https://github.com/ecomfe/gitdiff-parser/pull/25/files, which is a dep of a dep. you can find the right file by changing the url from `../DiffApp/..` to `../RnDiffApp/..`.

I am thinking of removing this file actually, as `react-native upgrade` will soon be good enough to replace the usage file. But I would gladly accept a PR to make...

Yep. Key was here is **was**. I think it will be much better soon! And I hope we can keep it working well for a long time. :)

I have also made https://pvinis.github.io/purge-web/ so its easy to find the diff you need.

Hello. I would suggest to go version by version. It will make it easier even if it's a bit slower. The best way is to start with the diff, make...

I have been toying around with xcodegen which will make things waaaay easier. After 0.60 I will make it and make a PR. It should be easier, since the autolinking...

Closing this. We have instructions here https://github.com/react-native-community/upgrade-helper#%EF%B8%8F-how-to-use. This is a pretty old issue too.