Thank you for your interest in contributing to the Google SecOps Wrapper SDK! This document provides an overview of the contribution process.
-
Create an Issue
- Describe the bug or feature you want to address
- Get feedback on your approach and proposed change
-
Fork and Branch
- Fork the repository and create a branch for your changes
-
Code and Test
- Follow the AUTHORING_GUIDE for coding guidelines and best practices.
- Add tests for new code (see TESTING)
- Keep changes focused and related to the issue
-
Submit Pull Request
- Sign the Google CLA if you haven't already
- Reference related issues in your PR description
Before we can take contributions, 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. This is a one-time process, after which you will be free to submit pull requests.