ci: add CLA assistant workflow#12
Merged
Merged
Conversation
Adds the Contributor License Agreement workflow using the Splunk CLA assistant, matching the configuration used in splunk-otel-python-contrib. Uses pinned action hash instead of a mutable version tag. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
splunk/cla-agreement)contributor-assistant/github-actionto its SHA hash (ca4a40a7d1004f18d9960b404b97e5f30a505a08= v2.6.1) instead of a mutable version tagHow it works
I have read the CLA Document and I hereby sign the CLAdependabot[bot]is allowlisted and does not need to signRequired secrets
PAT_CLATOOL: personal access token with permissions to write tosplunk/cla-agreementsignatures file (same secret used across Splunk OSS repos)Test plan
Made with Cursor