Currently the user flow for users is to download the library from this github repo. We want to make it so that the user flow is reduced to simply installing from the IDE library manager.
To do this, we'll need to publish our library to the official Arduino Library Registry^1. It appears to be that everything is automated using GH Actions^2. Not sure if it's worth integrating some of these checks to any feature merges to our release branch.
Description
Currently the user flow for users is to download the library from this github repo. We want to make it so that the user flow is reduced to simply installing from the IDE library manager.
To do this, we'll need to publish our library to the official Arduino Library Registry^1. It appears to be that everything is automated using GH Actions^2. Not sure if it's worth integrating some of these checks to any feature merges to our release branch.
Requirements:
contributing.md
git versioning semanticsCC-Library-Lantern
forkSuggested Solution
Contribution to the library-registry^1
Alternatives
Additional Notes