Contribution Guide

Last updated 2 months ago

Was this helpful?

Contribution Guide

KubeArmor maintainers welcome individuals and organizations from across the cloud security landscape (creators and implementers alike) to make contributions to the project. We equally value the addition of technical contributions and enhancements of documentation that helps us grow the community and strengthen the value of KubeArmor. We invite members of the community to contribute to the project!

To make a contribution, please follow the steps below.

Fork this repository (KubeArmor)
First, fork this repository by clicking on the Fork button (top right).
Then, click your ID on the pop-up screen.
This will create a copy of KubeArmor in your account.
Clone the repository
Now clone Kubearmor locally into your dev environment.
```
 $ git clone https://github.com/[your GitHub ID]/KubeArmor
```
This will clone a copy of Kubearmor installed in your dev environment.
Make changes
First, go into the repository directory and make some changes.
Please refer to to set up your environment for KubeArmor contribution.
Check the changes
If you have changed the core code of KubeArmor then please run tests before committing the changes
```
cd tests
~/KubeArmor/tests$ make
```
If you see any warnings or errors, please fix them first.
If some tests are failing, then fix them by following
If you have made changes in Operator or Controller, then follow
Commit changes
Please see your changes using "git status" and add them to the branch using "git add".
```
 $ cd KubeArmor
 ~/KubeArmor$ git status
 ~/KubeArmor$ git add [changed file]
```
Then, commit the changes using the "git commit" command.
```
 ~/KubeArmor$ git commit -s -m "Add a new feature by [your name]"
```
Please make sure that your changes are properly tested on your machine.
Push changes to your forked repository
Push your changes using the "git push" command.
```
 ~/KubeArmor$ git push
```
Create a pull request with your changes with the following steps
First, go to your repository on GitHub.
Then, click "Pull request" button.
After checking your changes, click 'Create pull request'.
A pull request should contain the details of all commits as specific as possible, including "Fixes: #(issue number)".
Finally, click the "Create pull request" button.
The changes would be merged post a review by the respective module owners. Once the changes are merged, you will get a notification, and the corresponding issue will be closed.
DCO Signoffs
To ensure that contributors are only submitting work that they have rights to, we are requiring everyone to acknowledge this by signing their work. Any copyright notices in this repo should specify the authors as "KubeArmor authors".
To sign your work, just add a line like this at the end of your commit message:
```
Signed-off-by: FirstName LastName <email@address.com>
```
This can easily be done with the -s or --signoff option to git commit.
By doing this, you state that the source code being submitted originated from you (see https://developercertificate.org).

PreviousFAQs NextDevelopment Guide

Last updated 2 months ago

Was this helpful?

To make a contribution, please follow the steps below.

Fork this repository (KubeArmor)
First, fork this repository by clicking on the Fork button (top right).
Then, click your ID on the pop-up screen.
This will create a copy of KubeArmor in your account.
Clone the repository
Now clone Kubearmor locally into your dev environment.
```
 $ git clone https://github.com/[your GitHub ID]/KubeArmor
```
This will clone a copy of Kubearmor installed in your dev environment.
Make changes
First, go into the repository directory and make some changes.
Please refer to to set up your environment for KubeArmor contribution.
Check the changes
If you have changed the core code of KubeArmor then please run tests before committing the changes
```
cd tests
~/KubeArmor/tests$ make
```
If you see any warnings or errors, please fix them first.
If some tests are failing, then fix them by following
If you have made changes in Operator or Controller, then follow
Commit changes
Please see your changes using "git status" and add them to the branch using "git add".
```
 $ cd KubeArmor
 ~/KubeArmor$ git status
 ~/KubeArmor$ git add [changed file]
```
Then, commit the changes using the "git commit" command.
```
 ~/KubeArmor$ git commit -s -m "Add a new feature by [your name]"
```
Please make sure that your changes are properly tested on your machine.
Push changes to your forked repository
Push your changes using the "git push" command.
```
 ~/KubeArmor$ git push
```
Create a pull request with your changes with the following steps
First, go to your repository on GitHub.
Then, click "Pull request" button.
After checking your changes, click 'Create pull request'.
A pull request should contain the details of all commits as specific as possible, including "Fixes: #(issue number)".
Finally, click the "Create pull request" button.
The changes would be merged post a review by the respective module owners. Once the changes are merged, you will get a notification, and the corresponding issue will be closed.
DCO Signoffs
To ensure that contributors are only submitting work that they have rights to, we are requiring everyone to acknowledge this by signing their work. Any copyright notices in this repo should specify the authors as "KubeArmor authors".
To sign your work, just add a line like this at the end of your commit message:
```
Signed-off-by: FirstName LastName <email@address.com>
```
This can easily be done with the -s or --signoff option to git commit.
By doing this, you state that the source code being submitted originated from you (see https://developercertificate.org).