Contributions to Matter Hooks are always welcome!
We welcome bug reports, suggestions, and code contributions. We want Matter Hooks to be a project everyone feels they can use and be a part of.
Matter Hooks and those participating in any of its spaces are governed by its code of conduct. By participating you are also expected to uphold this code. Report any unacceptable behavior to [email protected].
If you found a bug, please let us know about it by submitting a GitHub issue.
Be sure to:
- Check that an issue hasn't already been submitted about it. If you find one, please provide any additional information there.
- Provide a clear descriptive title and a detailed description of the problem
- Explain how and when the problem occurs and what steps to take to reproduce the problem
Thank you!
- Open a pull request against the
main
branch - Clearly describe the problem and solution in the pull request
- Include any relevant issue number
Great!
- Create an issue suggesting the feature
- We love when people contribute, but we hate for their effort to be wasted. Discussing the issue ahead of time can ensure the code you write will be accepted.
- Fork the project, and start writing
- When you're done, be sure to open a pull request against
main
- Include the issue number for the associated issue
- Consider opening a draft pull request right away. This is the best way to discuss the code as you write it.
We appreciate your enthusiasm, however cosmetic code patches are unlikely to be approved. We do care about code quality, but the cost typically outweighs the benefit of the change.
Releases for Matter Hooks are made by a maintainer using a release branch and a pull request.
- Create a new release branch
- Update
CHANGELOG.md
- Bump the version in
wally.toml
according to semver guidelines - Create a pull request against
main
- Review to ensure a stable release
- Make any necessary changes (be sure to keep
CHANGELOG.md
accurate) - Squash and merge the pull request
- Push a new version tag
- Write GitHub release notes