-
Notifications
You must be signed in to change notification settings - Fork 9
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) Resolve conflicts with gatsby-i18n-source @ 90932a0 #14
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like there's a lot of new English text that require translations.
Thanks @tesseralis, yes and I added a new task in #1 for the partial translations. All conflicts are resolved now, should we merge this? |
@asantarissy My preference would be to re-translate the conflicts in this PR. If we merge this as-is, it would lead to pages with half-English, half-Arabic content, which can be jarring for readers. It's better to have an outdated version of a fully-translated file, in my opinion. If you feel like the changes are big enough that you'd like a separate PR for them, you can create a new branch off this one and create a PR against it. See the translation sync guide for more information. |
Sync conflicts with the source repo. Please update the translations based on updated source content.
For more information on how to resolve sync conflicts, check out the guide for syncing translations.
The following 7 files have conflicts:
Once all the commits have been fixed, mark this pull request as "Ready for review" and merge it in!
See all changes since the last sync here:
https://github.com/gatsbyjs/gatsby-i18n-source/compare/d1b72e5..90932a0
NOTE: Do NOT squash-merge this pull request. The sync script requires a ref to the source repo in order to work correctly.
Related PRs
#13 PR for syncing non-conflicting files