This pull request updates the documentation to provide alternative download links for users in China, addressing potential issues with slow or unstable connections to GitHub. The changes include adding references to the Jihulab mirror in the installation and troubleshooting guides.

Documentation updates for users in China:

docs/en/installing.rst: Added a note and alternative repository link (https://jihulab.com/esp-mirror/espressif/arduino-esp32.git) for users in China experiencing slow download speeds. Also included stable and development release JSON file links for the Arduino IDE Boards Manager.[1][2]
docs/en/troubleshooting.rst: Added a new section titled "Slow or unstable downloads" with Jihulab mirror links for the repository and JSON files, providing guidance for users facing connection issues.

Requires#11288 to be consistent.

lucasssvaz added the Type: DocumentationIssue pertains to Documentation of Arduino ESP32 label

Apr 28, 2025

lucasssvaz requested review frompedrominatel andme-no-dev

April 28, 2025 14:34

lucasssvaz self-assigned this

Apr 28, 2025

Copy link

Contributor

github-actionsbot commentedApr 28, 2025•
edited
Loading

	Messages
📖	🎉 Good Job! All checks are passing!

👋Hello lucasssvaz, we appreciate your contribution to this project!

📘 Please review the project'sContributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by thePR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with eachpush event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger isnot a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manuallyretry these Danger checks, please navigate to theActions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫dangerJS against50596c6