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

Tasmota changes #179

Merged
merged 49 commits into from
Jul 2, 2024
Merged

Tasmota changes #179

merged 49 commits into from
Jul 2, 2024

Conversation

Jason2866
Copy link
Collaborator

No description provided.

Jason2866 added 30 commits March 8, 2024 15:21
Copy link

github-actions bot commented Jul 2, 2024

Fails
🚫
    The target branch for this pull request should be `master`.

    If you would like to add this feature to the release branch, please state this in the PR description and we will consider backporting it.
Warnings
⚠️ The PR description looks very brief, please check if more details can be added.
⚠️

Some issues found for the commit messages in this MR:

  • the commit message Create a PHY instance of JL1101 appears to be a temporary or automatically generated message
  • the commit message Create esp_eth_phy_jl1101.c appears to be a temporary or automatically generated message
  • the commit message Create package.json appears to be a temporary or automatically generated message
  • the commit message Create version.txt appears to be a temporary or automatically generated message
  • the commit message Update Kconfig appears to be a temporary or automatically generated message
  • the commit message Update dac_continuous.c appears to be a temporary or automatically generated message
  • the commit message Update entity.py appears to be a temporary or automatically generated message
  • the commit message Update esp_psram_impl_quad.c appears to be a temporary or automatically generated message
  • the commit message Update install.sh appears to be a temporary or automatically generated message
  • the commit message Update mac_addr.c appears to be a temporary or automatically generated message
  • the commit message Update package.json appears to be a temporary or automatically generated message
  • the commit message Update package.json appears to be a temporary or automatically generated message
  • the commit message Update release_zips.yml appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update soc.h appears to be a temporary or automatically generated message
  • the commit message Update version.txt appears to be a temporary or automatically generated message
  • the commit message Update version.txt appears to be a temporary or automatically generated message
  • the commit message add jl1101 may not be sufficiently descriptive

Please consider updating these commit messages.

Messages
📖 You might consider squashing your 49 commits (simplifying branch history).

👋 Welcome Jason2866, thank you for your first contribution to espressif/esp-idf project!

📘 Please check Contributions Guide for the contribution checklist, information regarding code and documentation style, testing and other topics.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for espressif/esp-idf project.

Pull request review and merge process you can expect

Espressif develops the ESP-IDF project in an internal repository (Gitlab). We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub 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 master branch
  6. On next sync from the internal git repository merged change will appear in this public Github repository

🔁 You can re-run automatic PR checks by retrying the DangerJS action

Generated by 🚫 dangerJS against d6021f8

@Jason2866 Jason2866 merged commit 01c738d into release/v5.2 Jul 2, 2024
2 of 4 checks passed
@Jason2866 Jason2866 deleted the release/v5.2_work branch July 2, 2024 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant