0.57.3, 0.57.4

Question

0.57.3, 0.57.4

raphaelhovsepyan opened this issue 6 years ago · comments

It's just a reminder that new 2 versions are released 18 days ago and 5 day ago

Pavlos Vinieratos · Answer 1 · Wed Oct 31 2018 00:25:39 GMT+0800 (China Standard Time)

I kinda gave up on this repo, mostly because I have always found git upgrade very awkward and troublesome. I have https://GitHub.com/pvinis/rn-diff-purge if you are interested, which is easier for me to keep up, and use.

…

-- Pavlos Vinieratos

On 30 October 2018 at 16:51:39, Raphael Hovsepyan ***@***.******@***.***)) wrote: It's just a reminder that new 2 versions are released 18 days ago and 5 day ago — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub(#39), or mute the thread(https://github.com/notifications/unsubscribe-auth/AAGHiZDnNAOM97ftlXjxHbhbXSlfF5Syks5uqHWLgaJpZM4YCQBU).

Raphael Hovsepyan · Answer 2 · Wed Oct 31 2018 00:58:41 GMT+0800 (China Standard Time)

awesome thanks

MrHubble · Answer 3 · Fri Nov 02 2018 11:34:10 GMT+0800 (China Standard Time)

@pvinis In your repo I see you link to the the procedure as described by in this repo?

The procedure isn't really straightforward but it's still more efficient than using the upgrade command:
1 Download the git patch
2 Prepare the patch
3 Set up the 3-way merge
4 Run the apply command

Is it safe to assume that that's how you're using rn-diff-purge?

Pavlos Vinieratos · Answer 4 · Fri Nov 02 2018 12:50:50 GMT+0800 (China Standard Time)

op. where is that? ill make sure to change it. i have changed the script and it deletes the old and creates a new project and then diffs.

Pavlos Vinieratos · Answer 5 · Fri Nov 02 2018 13:07:40 GMT+0800 (China Standard Time)

I have updated the readme. if there is any place that still references this repo's way, let me know.

MrHubble · Answer 6 · Fri Nov 02 2018 13:58:45 GMT+0800 (China Standard Time)

This is where it links to the usage details:

Pavlos Vinieratos · Answer 7 · Fri Nov 02 2018 14:19:58 GMT+0800 (China Standard Time)

should be all fine now. also, sorry to "pollute" this repo's issues for this. and thanks for pointing out the errors on my repo. :)

MrHubble · Answer 8 · Fri Nov 02 2018 14:45:45 GMT+0800 (China Standard Time)

Thanks for the new repo and for the clarification. Apparently react-native-git-upgrade is not well maintained so I'm looking forward to using your alternative.

Pavlos Vinieratos · Answer 9 · Fri Nov 02 2018 14:57:59 GMT+0800 (China Standard Time)

it has been a hard problem for a while now. that's what lead me to rn-diff and I'm thankful for this repo, but often I was doing the purge thing in addition, to make sure I'm not missing something. so now I am not depending on git-upgrade at all, and do it my way, which in my opinion is the cleanest way.

let me know of any concerns/suggestions, over at the purge repo.

I'm happy if it's useful for more people than just me! :D