We welcome all contributions, suggestions, and feedback, so please do not hesitate to reach out!
Before you contribute, please take a moment to review and agree to abide by our community Code of Conduct.
The Kyverno website has the most updated information on how to engage with the Kyverno community including its maintainers and contributors. There are three classes of contributors possible: Contributor, Code Owner, and Maintainer. Please see the Contributing section on the website for the requirements and privileges afforded to each.
Join our community meetings to learn more about Kyverno and engage with other contributors.
Issues to Kyverno help improve the project in multiple ways including the following:
- Report potential bugs
- Request a feature
- Request a sample policy
The Kyverno website, like the main Kyverno codebase, is stored in its own git repo. To get started with contributions to the documentation, follow the guide on that repository.
Pull requests (PRs) allow you to contribute back the changes you've made on your side enabling others in the community to benefit from your hard work. They are the main source by which all changes are made to this project and are a standard piece of GitHub operational flows.
New contributors may easily view all open issues labeled as good first issues allowing you to get started in an approachable manner.
Head over to the project repository on GitHub and click the "Fork" button. With the forked copy, you can try new ideas and implement changes to the project.
- Clone the repository to your device:
Get the link of your forked repository, paste it in your device terminal and clone it using the command.
git clone https://hostname/YOUR-USERNAME/YOUR-REPOSITORY- Create a branch:
Create a new brach and navigate to the branch using this command.
git checkout -b <new-branch>Great, it's time to start hacking! You can now go ahead to make all the changes you want.
- Stage, Commit, and Push changes:
Now that we have implemented the required changes, use the command below to stage the changes and commit them.
git add .git commit -s -m "Commit message"The -s signifies that you have signed off the commit.
Go ahead and push your changes to GitHub using this command.
git pushFor contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project, we are requiring everyone to acknowledge this by signing their work which indicates you agree to the DCO found here.
To sign your work, just add a line like this at the end of your commit message:
Signed-off-by: Random J Developer <[email protected]>This can easily be done with the -s command line option to append this automatically to your commit message.
git commit -s -m 'This is my commit message'Review the release process.