Want to contribute? Great! First, read this page (including the small print at the end).
Starlark files should be formatted by buildifier. We suggest using a pre-commit hook to automate this. First install pre-commit, then run
pre-commit installOtherwise the Buildkite CI will yell at you about formatting/linting violations.
Before we can use your code, you must sign the Google Individual Contributor License Agreement (CLA), which you can do online.
The CLA is necessary mainly because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things for instance that you'll tell us if you know that your code infringes on other people's patents. You don't have to sign the CLA until after you've submitted your code for review and a member has approved it, but you must do it before we can put your code into our codebase.
Before you start working on a larger contribution, you should get in touch with us first. Use the issue tracker to explain your idea so we can help and possibly guide you.
Before starting a complex contribution we strongly encourage you to share a design document.
Here you can find a document template.
All submissions, including submissions by project members, require review. We use GitHub's code review system to suggest changes, then merge the changes to master when the PR is green and reviewed. The changes will then be in the next release.
Contributions made by corporations are covered by a different agreement than the one above, the Software Grant and Corporate Contributor License Agreement.