Skip to content

fix: Updated the tools options for Geekble Mini #11437

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: Updated the tools options for Geekble Mini #11437

wants to merge 1 commit into from
+0 −38

Conversation

syong0921
Copy link
Contributor

fix: Updated the tools options for Geekble Mini

Description of Change

Geekble Mini is a Module for Arduino - ESP beginners
We thought Geekble Mini still have too much options, which can confuse beginners
So deleted rarely used options

Tests scenarios

Tested under Arduino IDE v2.3.6, Arduino-esp32 core v3.2.0 with Geekble Mini

Related links

@syong0921
fix: Updated the tools options for Geekble Mini
2df43f6 
fix: Updated the tools options for Geekble Mini
@syong0921 syong0921 requested a review from P-R-O-C-H-Y as a code owner June 4, 2025 20:57
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 4, 2025

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello syong0921, 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.
- 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 2df43f6

P-R-O-C-H-Y
P-R-O-C-H-Y approved these changes Jun 5, 2025
View reviewed changes
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.

LGTM

@P-R-O-C-H-Y P-R-O-C-H-Y added Status: Pending Merge Pull Request is ready to be merged Type: 3rd party Boards labels Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@P-R-O-C-H-Y P-R-O-C-H-Y P-R-O-C-H-Y approved these changes

Assignees
No one assigned
Labels
Status: Pending Merge Pull Request is ready to be merged Type: 3rd party Boards
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@syong0921 @P-R-O-C-H-Y