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 with upstream @ 2d5be7b7 #107

Open
wants to merge 1,632 commits into
base: master
from
Open

Sync with upstream @ 2d5be7b7 #107

wants to merge 1,632 commits into from

Conversation

@javascript-translate-bot
Copy link

@javascript-translate-bot javascript-translate-bot commented Oct 26, 2020

This PR was automatically generated to merge changes from en.javascript.info at 2d5be7b

Conflicted files in this PR have labels ">>>..." with both sides of conflict. If you merge this PR, you'll need to examine the listed files and resolve conflicts.

Alternatively, you can close this PR and merge conflicting changes manually.

The following files have conflicts and may need updates of the translations:

Click to open a list of 33 files

To merge changes manually (instead of merging this PR):

  1. Add remote upstream that links to the English version (only needs to be done once)
    • git add remote upstream https://github.com/javascript-tutorial/en.javascript.info
  2. Commit all current work locally and git checkout master
  3. Pull the recent changes from the English version:
    • git pull upstream master
  4. Deal with the conflicts. If a conflict touches a few lines, then just fix it. Otherwise, following commands can help:
    • Checkout your (translated) version of a file/folder at the given path (removes all upstream changes):
      • git checkout --ours <path>
    • See the diff, what changed in the upstream file since branches diverged:
      • git diff --word-diff master...upstream/master <path> (please note: three dots in the command)
    • Then you can examine the changes in upstream and add them manually
  5. When conflicts resolved, commit them and git push origin master

Please ignore changes in README.md (git checkout --ours README.md && git commit -m ignore README.md).

This PR will be closed and replaced with a new one in a few days.

iliakan and others added 30 commits Aug 27, 2020
add semicolon
once in -> once every
Improve phrasing
Typos
Fixed "compatibility" spelling error
5.4 - change 7 basic types to eight basic types
The solution here had no break, an infinite loop. Modified to match plunker example code
Typos
clarifying example code
Typos
Update article.md
Typos
Update article.md with link to Brython
plis check my syntax , I can't test
internal link format  info:
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
Co-authored-by: Muhammed Zakir <8190126+MuhammedZakir@users.noreply.github.com>
iliakan and others added 27 commits Oct 20, 2020
Currently, the error is alerted and the console is empty (at least in Chrome).
Remove possibly outdated comment
FIX: change ; to ,
FIX: delete extra space
One addition and one fix
Fix typo in 1.4.7 (optional chaining)
Mention function declaration in 1.6.5 (global object)
Fix a typo in 1.6.6 (function object, NFE)
Fix possible typo in 1.6.7 ("new Function" syntax)
Fix typos, specify link in 1.6.8 (Scheduling)
@javascript-translate-bot javascript-translate-bot requested a review from javascript-tutorial/translate-vi Oct 26, 2020
@CLAassistant
Copy link

@CLAassistant CLAassistant commented Oct 26, 2020

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
4 out of 7 committers have signed the CLA.

iliakan
joaquinelio
leviding
vsemozhetbyt
lex111
dorelljames
aruku
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

You can’t perform that action at this time.