The “CLA” lite tool uses Github to track users who have agreed to the CLA for /splunk projects. Developers can rely on CI checks to determine if a PR from an outside source can be merged without manually consulting third-party systems like SFDC, which is error prone. When properly used this fully automates the requirements of our contribution program.
Note: Splunk employees should read the internal version of this document instead.
Splunk open-source project maintainers
Splunk developers may opt into this solution by doing the following:
- Add workflows/agreements.yaml to their github repo in .github/workflows using the main branch. You can use this premade agreements.yaml file if necessary.
- Enable branch protection for main, develop, and any other merge targets with the requirement of passing the agreements status check. Add a repository secret PAT_TOKEN with a Github Personal Access Token (PAT) for a service account to your repo. This token should include the repo scope, and you must manually add it in the repo’s secret.
This CLA/COC tracker users https://github.com/marketplace/actions/cla-assistant-lite. Thank you SAP for your support of the OSS/Shared source Community.