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

fix(esp_http_client): correct the typo in the error log string (IDFGH-11686) #12796

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

s1tnk
Copy link
Contributor

@s1tnk s1tnk commented Dec 14, 2023

Corrected the module name in the error log.

Corrected the module name in the error log.
("https_ota" to "http_client")
Copy link

Warnings
⚠️ The Pull Request description looks very brief, please check if more details can be added.

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


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

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


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

DangerJS is triggered with each push 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 is not 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 manually retry these Danger checks, please navigate to the Actions 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against c5cb67d

@espressif-bot espressif-bot added the Status: Opened Issue is new label Dec 14, 2023
@github-actions github-actions bot changed the title fix(esp_http_client): correct the typo in the error log string fix(esp_http_client): correct the typo in the error log string (IDFGH-11686) Dec 14, 2023
@mahavirj
Copy link
Member

sha=c5cb67d49c1c77c2d6706742622e41631b20f9d1

@mahavirj mahavirj added the PR-Sync-Merge Pull request sync as merge commit label Dec 14, 2023
@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: Opened Issue is new labels Dec 14, 2023
@espressif-bot espressif-bot merged commit 3e22e0b into espressif:master Dec 18, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR-Sync-Merge Pull request sync as merge commit Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants