Sync with react.dev @ b1a249d5

[react-translations-bot]

This PR was automatically generated.

Merge changes from react.dev at b1a249d

The following files have conflicts and may need new translations:

• src/content/learn/react-developer-tools.md

Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.

DO NOT SQUASH MERGE THIS PULL REQUEST!

Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
pl-legacy-reactjs-org	⬜️ Ignored (Inspect)	Visit Preview		Mar 16, 2025 9:19am

[github-actions]

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[dawidsabat]

@jakubdrozdek, as a Collaborator, am I entitled to review, resolve conflicts in such sync PRs and merge them? Everything was fine with this one? Anything to improve or remember?

I am not that much familiar with Github flow so these might be silly questions 😄

[jakubdrozdek]

@dawidsabat These PRs are created by the sync bot, to let us know that the original repo has been changed in one of the translated files.
You just need to resolve conflicts by translating the new words (by editing our translation), updating urls and paths in hrefs, etc.
The bot doesn't complain about files that were changed in their repo but never touched in ours - it merges them clearly, without conflicts.
Once you approve, make sure to merge this PR to our repo (never squash-merge, as explained in the PR description). Otherwise, the bot will complain about the same conflicts in the future.

[dawidsabat]

Ok, understood. Thanks!