Skip to content

Latest commit

 

History

History
69 lines (50 loc) · 2.66 KB

CONTRIBUTING.md

File metadata and controls

69 lines (50 loc) · 2.66 KB

Contributing

Interested in contributing to TensorFlow Probability? We appreciate all kinds of help!

Pull Requests

We gladly welcome pull requests.

Before making any changes, we recommend opening an issue (if it doesn't already exist) and discussing your proposed changes. This will let us give you advice on the proposed changes. If the changes are minor, then feel free to make them without discussion.

Want to contribute but not sure of what? Here are a few suggestions:

  1. Add a new example or tutorial. Located in examples/, these are a great way to familiarize yourself and others with TFP tools.

  2. Solve an existing issue. These range from low-level software bugs to higher-level design problems. Check out the label good first issue.

All submissions, including submissions by project members, require review. After a pull request is approved, we merge it. Note our merging process differs from GitHub in that we pull and submit the change into an internal version control system. This system automatically pushes a git commit to the GitHub repository (with credit to the original author) and closes the pull request.

Style

See the TensorFlow Probability style guide.

Unit tests

Please include unit tests when contributing new features, as they help to a) prove that your code works correctly, and b) guard against future breaking changes to lower the maintenance cost. It's also helpful to check that any changes you propose do not break existing unit tests. You can run tests (on CPU) using the command,

bazel test --config=opt --copt=-O3 --copt=-march=native \
  //tensorflow_probability/...

or on GPU,

bazel test --config=opt --copt=-O3 --copt=-march=native --config=cuda \
  //tensorflow_probability/...

from the root of the tensorflow_probability repository.

Contributor License Agreement

Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to https://cla.developers.google.com/ to see your current agreements on file or to sign a new one.

You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again.