Skip to content

Latest commit

 

History

History
66 lines (47 loc) · 2.52 KB

CONTRIBUTING.md

File metadata and controls

66 lines (47 loc) · 2.52 KB
Raw

How to become a contributor and submit your own code

Contributor License Agreements

We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

  • If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an individual CLA.
  • If you work for a company that wants to allow you to contribute your work, then you'll need to sign a corporate CLA.

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.

How to Build and Test

  1. bazel build //... to build the whole project or ex:bazel build //base:static_root_amd64_debian17 for a single image

  2. For running tests, check ./test.sh. (bazel test //... will NOT run all tests, as many tests are marked "manual".)

  3. For building and loading images to your local Docker engine, you need to add a new rule for that image to the BUILD:

load("@rules_oci//oci/private:tarball.bzl", "oci_tarball")

oci_tarball(
    name = "local_build",
    image = "//base:static_root_amd64_debian17",
    repo_tags = [],
)

then build the tarball and load it into docker

bazel build //:local_build
docker load --input $(bazel cquery --output=files //:local_build)

Code style

For styling Bazel files, install and run buildifier with:

# Install buildifier version 3.2.0
go install github.com/bazelbuild/buildtools/buildifier@latest

# This will automatically fix files.
buildifier -mode=fix $(find . -name 'BUILD*' -o -name 'WORKSPACE*' -o -name '*.bzl' -type f)

For styling Python files, install and run pylint with:

# Install pylint
sudo pip install pylint
# Or
sudo apt-get install pylint

# Identify python style issues.
find . -name "*.py" | xargs pylint --disable=R,C

Contributing a Patch

  1. Submit an issue describing your proposed change to the repo in question.
  2. The repo owner will respond to your issue promptly.
  3. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
  4. Fork the desired repo, develop and test your code changes.
  5. Submit a pull request.