Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync original #91

Merged
merged 47 commits into from
Feb 7, 2019
Merged

Sync original #91

merged 47 commits into from
Feb 7, 2019

Conversation

tesseralis
Copy link
Member

@tesseralis tesseralis commented Feb 6, 2019

Doing this manually since there's a ton of commits.

The only page that has interfering translations is hooks-intro.md. It seems like the git merge is pretty smart about only creating a conflict where the english text has changed!

https://github.com/reactjs/ja.reactjs.org/pull/91/files#diff-daed9eb3a7702fb9fe0397b0f613d4faL8

gaearon and others added 30 commits January 24, 2019 18:07
* add warning for invalid hook call

* Fix versions

* Split code examples

* unnecessary comma

* tweaks

* Update content/warnings/invalid-hook-call-warning.md

Co-Authored-By: gaearon <dan.abramov@gmail.com>

* nit
@tesseralis tesseralis mentioned this pull request Feb 6, 2019
90 tasks
@smikitky
Copy link
Member

smikitky commented Feb 7, 2019

Wow, I was anticipating something very tedious, but there are only four conflicts and all of them are fairly easy to resolve :)

So should I directly push to this branch to resolve conflicts?

@tesseralis
Copy link
Member Author

Haha, the spanish fork translated more hooks articles so they have more conflicts :P

Just direct push to the branch!

@smikitky
Copy link
Member

smikitky commented Feb 7, 2019

Done!

Actually this merge has changes that involve several ongoing PRs, but I'll take care of notifying the translators.

@smikitky
Copy link
Member

smikitky commented Feb 7, 2019

@koba04 @potato4d Can either of you take a brief look? The only four conflicts have been resolved in 566d932, and everything else seems to have been automatically merged.

And will we really squash-marge this?

@koba04
Copy link
Member

koba04 commented Feb 7, 2019

@smikitky I think it shouldn't squash-merge. it should keep the original commits.

@smikitky
Copy link
Member

smikitky commented Feb 7, 2019

Okay, I re-enabled merge commits.

@smikitky
Copy link
Member

smikitky commented Feb 7, 2019

@koba04 Could you approve? We should merge this PR before @takanorip and I can update the corresponding PRs.

@koba04
Copy link
Member

koba04 commented Feb 7, 2019

@smikitky OK, I'll review this soon 🚀

@koba04
Copy link
Member

koba04 commented Feb 7, 2019

done

@smikitky smikitky merged commit 5c00209 into master Feb 7, 2019
@smikitky smikitky deleted the sync-original branch February 7, 2019 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants