Skip to content

Latest commit

 

History

History
52 lines (42 loc) · 2.2 KB

CONTRIBUTING.md

File metadata and controls

52 lines (42 loc) · 2.2 KB

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).

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.

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. Ensure that your code adheres to the existing style in the sample to which <<<<<<< HEAD you are contributing. Refer to the [Google Cloud Platform Samples Style Guide] (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the recommended coding standards for this organization.
  6. Ensure that your code has an appropriate set of unit tests which all pass. Set up Travis to run the unit tests on your fork.
  7. Submit a pull request. ======= you are contributing.
  8. Ensure that your code has an appropriate set of unit tests which all pass. Set up Travis to run the unit tests on your fork.
  9. Submit a pull request.

Style

Samples in this repository follow the PSR2 and PSR4 recommendations. This is enforced using PHP CS Fixer.

5f54c719ced870d4327a38823aea4906d88e15f9