Undo fork from #11463

[JmillsExpensify]

We're forking a fork, which isn't ideal and we should undo and point upstream as soon as the PR mentioned in the HOLD is merged. I'm going to start this off as a monthly and we can re-assess from there.

Related issue: #11463

[JmillsExpensify]

Still on hold and probably will be for quite some time.

[JmillsExpensify]

Taking this issue off hold per this news.

[flodnv]

So what do I need to do? 😂 It feels like the only good path forward is to wait for a release and merge that rnw release back into our fork @roryabraham ?

[flodnv]

Maybe this PR resolves this issue? 😂 Expensify/react-native-web#14

[roryabraham]

To me it doesn't look like these commits are included in Expensify/react-native-web#14.

However, I'm overall I'm confused by this issue because I suspect there are a number of custom changes we have in our react-native-web fork, and we can't go back to using the upstream until all of those changes are merged and released upstream. For example, Expensify/react-native-web#11 was just merged a few days ago and IIRC the maintainer of react-native-web had no plans to review the upstream PR until at least after RNW 0.19 is released.