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

feat(boards): add Waveshare ESP32-S3-Touch-AMOLED boards #10549

Merged
merged 12 commits into from
Nov 4, 2024

Conversation

wurongmin
Copy link
Contributor

1.I have added three products of ESP32S3: ESP32-S3-Touch-AMOLED-1.43, ESP32-S3-Touch-AMOLED-1.64, ESP32-S3-Touch-AMOLED-1.91.
2.Among them, ESP32-S3-Touch-AMOLED-1.91 has been sold online. The link below: https://www.waveshare.net/shop/ESP32-S3-Touch-AMOLED-1.91.htm. Others will be available soon.
3.I believe many people will like our product because it is able to customize their own board name. This will further strengthen our campaign.

Copy link
Contributor

github-actions bot commented Nov 1, 2024

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "Add files via upload":
    • summary looks empty
    • type/action looks empty
  • the commit message "Add files via upload":
    • summary looks empty
    • type/action looks empty
  • the commit message "Delete variants/waveshare_esp32_s3_touch_amoled_143/pins_arduino.h":
    • summary looks empty
    • type/action looks empty
  • the commit message "Delete variants/waveshare_esp32_s3_touch_amoled_164 directory":
    • summary looks empty
    • type/action looks empty
  • the commit message "Delete variants/waveshare_esp32_s3_touch_amoled_191 directory":
    • summary looks empty
    • type/action looks empty
  • the commit message "feat(boards): Add the variants":
    • summary looks too short
  • the commit message "feat(boards): Three variants of the development board were added":
    • body's lines must not be longer than 100 characters

Please fix these commit messages - here are some basic tips:

  • follow Conventional 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 the Conventional Precommit Linter).

⚠️ Please consider squashing your 12 commits (simplifying branch history).

👋 Hello wurongmin, we appreciate your contribution to 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.

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 against 1535829

@wurongmin
Copy link
Contributor Author

I have closed the previous pull request, and after the successful merger, I will delete the warehouse. I am really sorry if it has caused you trouble, and it really caused a lot of people

@P-R-O-C-H-Y
Copy link
Member

@wurongmin The boards are doubled in boards.txt file. Please declare each board only once. Can you fix it?

To ensure that each plate type only one
@wurongmin
Copy link
Contributor Author

Thank you especially for reminding me,Now I've changed it

Copy link
Member

@P-R-O-C-H-Y P-R-O-C-H-Y left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me :) Thank you for enhancing the pins_arduino.h file with detailed pinout.

@P-R-O-C-H-Y P-R-O-C-H-Y added the Status: Pending Merge Pull Request is ready to be merged label Nov 1, 2024
@me-no-dev me-no-dev merged commit 57d0dee into espressif:master Nov 4, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged Type: 3rd party Boards
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants