Contributions to this project must be accompanied by a Contributor License Agreement (CLA). You (or your employer) retain the copyright to your contribution; this simply permits us to use and redistribute your contributions as part of the project.
If you or your current employer have already signed the Google CLA (even if it was for a different project), you probably don't need to do it again.
Visit https://cla.developers.google.com/ to see your current agreements or to sign a new one.
In order to get access to the Google SecOps platform, you need to submit this form. The form will be triaged by our Partner Management team. We might reach out to get more details. If everything is resolved, you will receive a Development License and access to Google SecOps.
If you already have access to Google SecOps through mutual customers/partners, then you can skip this step and start contributing.
This project follows Google's Open Source Community Guidelines.
Please fork the repository to work on it. When your changes are ready you can open a Pull Request with your changes to the main repository's main branch.
- Read more about forking
- Read about the Fork & Pull Request Workflow
All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose.
- Validations: Ensure all automated checks pass.
- Ready for Review: If you opened your PR as a "Draft", please mark it as "Ready for Review" once all validations pass. This signals to maintainers that the code is ready for inspection.
- Version Bump: If you are modifying an existing content, remember to increase the version of that content. This is required for the changes to be released.
Before submitting your Pull Request, please review the Pull Request Template Checklist. Ensuring your contribution meets these criteria will help speed up the review process.