We are thrilled to have you join us as a contributor! The Keptn is a community-driven project and we greatly value collaboration. There are various ways to contribute to the Lifecycle Toolkit, and all contributions are highly valued. Please, explore the options below to learn more about how you can contribute.
Please make sure to read and observe our Code of Conduct.
-
Create an issue: If you have noticed a bug, want to contribute features, or simply ask a question that for whatever reason you do not want to ask in the Lifecycle Toolkit Channels in the CNCF Slack workspace, please search the issue tracker to see if someone else in the community has already created a ticket. If not, go ahead and create an issue.
-
Start contributing: We also have a list of good first issues. If you want to work on it, just post a comment on the issue.
This document lays out how to get you started in contributing to Keptn, so please read on.
If you are worried or don’t know where to start, check out our next section explaining what kind of help we could use and where you can get involved. You can reach out with the questions to Lifecycle Toolkit Channels on Slack and a mentor will surely guide you!
See Set up the development environment for information about how to set up an environment in which you can develop and test software for Keptn.
Please check Related Technologies.
Please check Linter Requirements.
See Working with Git
Your PR will usually be reviewed by the Keptn team within a couple of days, but feel free to let us know about your PR via Slack.
All commits must be accompanied by a DCO sign-off. See DCO for more information.