Welcome! Most documentation is hosted over at the Zephyr Documentation Site, but this README is here to give you a quick tour of what's what.
Zephyr, and it's sister-project Aire, are projects designed to help you quickly and easily build, test, and release modular applications.
If you've ever used GIMP, Adobe Photoshop, or Wordpress, then you've used an extensible application, which is very similar to a modular application. In fact, for many applications, extensible and modular may be used interchangeably.
Extensible applications are applications that can be extended by users, other vendors, or the application vendor themselves. As a user, you frequently interact with extensions as plugins--for instance, you may need a filter or format from your image-processing program that isn't provided by the vendor, so you locate the plugin you'd like to install from the list of plugins on their website or in their application and
Submitting a pull request will automatically trigger a build, as well as kick off PR linting.
To get the PR linting phase to pass, there are a few requirements:
- PR is assigned to the author (happens automatically with the github-actions bot)
- Body of PR includes the issue the PR is resolving. This should be the canonical link (e.g. #83)
- PR is added to Zephyr Development Board (should happen automatically, but may be outstanding issues with workflow)
A reviewer should also be assigned, but this is not required to get the linting to pass.