Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Sync with upstream @ d78b01e9 #374

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

Open
javascript-translate-bot wants to merge 3,731 commits into master
base: master
Choose a base branch
Loading
from sync-d78b01e9
Open

Conversation

@javascript-translate-bot
Copy link

@javascript-translate-bot javascript-translate-bot commented Dec 15, 2025

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

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 329 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.

wdscxsj and others added 30 commits September 29, 2022 23:13
Remove description of inconsistency between Chrome and Firefox
fix small typo in web-components slots chapter.
Same as title
iliakan and others added 27 commits March 24, 2025 23:52
Fix minor typo in Function object, NFE article.
..._JS_topic_Error-handling
Fix for #3826 - Removed errorception.com from the respective md file.
..._JS_topic_Error-handling
sentry.io added as per suggestion
Fix minor typo in Function binding article.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
clarify wording about null and undefined equality in JS
Copy link

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 16 committers have signed the CLA.

✅ smith558
✅ vincent-clipet
✅ iliakan
✅ wjw020206
❌ zakingslayerv22
❌ tonybishnoi
❌ nikoandpiko
❌ pj-szdm
❌ mhi1627
❌ AdityaGirdhar
❌ Gleb-Pastushenko
❌ dangerman
❌ Paramesh-T-S
❌ Lk-ux
❌ rahulrao0209
❌ cathoderay
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

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /