KubeArmor
Search…
Contribution Guide
If you want to make a contribution, please follow the steps below.
  1. 1.
    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.
  2. 2.
    Clone the repository
    Now clone Kubearmor locally into your dev environment.
    1
    $ git clone https://github.com/[your GitHub ID]/KubeArmor
    Copied!
This will clone a copy of Kubearmor installed in your dev environment.
  1. 1.
    Make changes
    First, go into the repository directory and make some changes.
    Please refer to development guide to set up your environment for KubeArmor contribution.
  2. 2.
    Check the changes
    Please run "test_kubearmor.sh" before committing the changes
    1
    cd KubeArmor/KubeArmor/build
    2
    ~/KubeArmor/KubeArmor/build$ ./test_kubearmor.sh
    Copied!
    If you see any warnings or errors, please fix them first.
  3. 3.
    Commit changes
    Please see your changes using "git status" and add them to the branch using "git add".
    1
    $ cd KubeArmor
    2
    ~/KubeArmor$ git status
    3
    ~/KubeArmor$ git add [changed file]
    Copied!
    Then, commit the changes using the "git commit" command.
    1
    ~/KubeArmor$ git commit -m "Add a new feature by [your name]"
    Copied!
    Please make sure that your changes are properly tested on your machine.
  4. 4.
    Push changes to your forked repository
    Push your changes using the "git push" command.
    1
    ~/KubeArmor$ git push
    Copied!
  5. 5.
    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. Also, please make sure that you have "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.
Last modified 1mo ago
Export as PDF
Copy link