Contributing guidelines
How to contribute to Awell's public extensions repository — discussions, issues, pull requests, coding style, and what to expect from review.
Awell's extensions are developed in the open. Contributions to the public awell-extensions repository
range from a question to a whole new extension.
This page is the contribution path referenced from the
awell-extensionsrepository README, so it's the canonical version. The repository points here.
Discussions, issues, and new extensions
Discussions
Use discussions for questions, ideas, and anything that isn't yet a concrete change.
Issues
Use issues for bugs and specific, actionable requests. Include the expected behavior, what happened instead, and how to reproduce it.
Create an extension
A new public extension is the most substantial contribution. See Build your own extension and Create an extension.
What to expect from review
Smaller pull requests move faster
Split a large change into focused pull requests wherever the work can be separated.
Review is about reliability
Expect review comments and iteration. A public extension ends up in other people's care flows, so review is about whether it holds up rather than how it's written.
Coding style follows the repository
Follow the conventions already in the repository. Extensions are TypeScript, and consistency with surrounding code matters more than personal preference.
License
Contributions are made under the repository's license.
Next steps
Back to Extensions.