Add support for ESP-IDF component registry #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
me-no-dev
force-pushed
the
feature/isp_idf_component_registry
branch
from
4bfb6d9 to
a38da77
Compare
me-no-dev
force-pushed
the
feature/isp_idf_component_registry
branch
from
040f7fe to
a38da77
Compare
mathieucarbou
approved these changes
Jan 28, 2025
me-no-dev
force-pushed
the
feature/isp_idf_component_registry
branch
from
a34e1ea to
6751bae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds full support for the IDF component registry, which includes workflow for uploading the component and example that can be used with ESP-IDF