Contributions are always welcome. Before contributing please read the
code of conduct and search the issue tracker; your issue may have already been discussed or fixed in master. To contribute, fork this repository, commit your changes, and send a Pull Request.
Note that our code of conduct applies to all platforms and venues related to this project; please follow it in all your interactions with the project and its participants.
Feature requests should be submitted in the Issue tracker, with a description of the expected behavior & use case, where they'll remain closed until sufficient interest, e.g. 👍 reactions, has been shown by the community.
Before submitting an Issue, please search for similar ones in the closed issues.
- Check our review guidelines.
- Ensure your change adhere to the technical and documentation requirements.
- Open separate pull requests to submit changes to multiple charts.
Pull requests approvals go through the following steps:
- A GitHub action is triggered to lint and test the chart's installation. For more information, see Chart testing.
- A maintainer reviews the changes. Any change requires at least one review.
- The pull request can be merged when at least one maintainer approves it.
Once the chart has been merged, it is automatically released.
Keep in mind that when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. If you'd like to execute our corporate CLA, or if you have any questions, please drop us an email at [email protected].
For more information about CLAs, please check out Alex Russell's excellent post, "Why Do I Need to Sign This?".