NotificationsYou must be signed in to change notification settings
Fork7.8k
Star15.9k

docs(3rd-party): Add section for third party tools#10749

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

me-no-dev merged 7 commits intoespressif:masterfromlucasssvaz:docs/3rdparty

Jan 7, 2025

Merged

docs(3rd-party): Add section for third party tools#10749

me-no-dev merged 7 commits intoespressif:masterfromlucasssvaz:docs/3rdparty

Jan 7, 2025

Conversation

Copy link

Member

lucasssvaz commentedDec 18, 2024

Description of Change

Add section for 3rd party tools in the documentation. Also fixes issues with dependencies in Python 3.13

Tests scenarios

Locally

Related links

#10045

lucasssvaz added3 commits

December 18, 2024 11:11

docs(3rd-party): Add section for third party tools

ec07892

fix(docs): Fix dependencies in Python 3.13

d8b1cc7

fix(typo): Fix docs typo

9ec03da

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

Dec 18, 2024

lucasssvaz requested review fromP-R-O-C-H-Y,SuGlider,me-no-dev,pedrominatel andrftafas

December 18, 2024 14:23

lucasssvaz self-assigned this

Dec 18, 2024

Copy link

Contributor

github-actionsbot commentedDec 18, 2024•
edited
Loading

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message`"fix(naming): Rename files"`: summary looks too short the commit message`"fix(typo): Fix docs typo"`: summary looks too short Please fix these commit messages - here are some basic tips: followConventional Commits style correct format of commit message should be:`<type/action>(<scope/component>): <summary>`, for example`fix(esp32): Fixed startup timeout issue` allowed types are:`change,ci,docs,feat,fix,refactor,remove,revert,test` sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) `TIP:` Install pre-commit hooks and run this check when committing (uses theConventional Precommit Linter).
⚠️	Please consider squashing your 7 commits (simplifying branch history).

👋Hello lucasssvaz, we appreciate your contribution to 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.
-Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- 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 againstebec20e