-
Notifications
You must be signed in to change notification settings - Fork 127
Add a check if contributor has signed Splunk Contributor License Agreement #1640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 20303360958Details
💛 - Coveralls |
patrykw-splunk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
why MR to main directly? |
.github/workflows/cla-check.yml
Outdated
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| # The below token should have repo scope and must be manually added by a maintainer in the GitHub Secrets | ||
| PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_ASSISTANT_PAT }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you add this secret? I don't see it in our secrets in GitHub.
What is the TTL of this PAT? Should we track and manage expiration date?
kubabuczak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say that we should merge it to develop.
Do you have an example of execution of this workflow?
.github/workflows/cla-check.yml
Outdated
|
|
||
| # the following fields are optional | ||
| remote-organization-name: splunk | ||
| remote-repository-name: splunk-operator-cla-signatures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where is this repository?
.github/workflows/cla-check.yml
Outdated
| uses: cla-assistant/github-action@v2.1.3-beta | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| PERSONAL_ACCESS_TOKEN: ${{ secrets.PAT_CLATOOL }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you create this secret? I don't see it in our secrets.
Description
What does this PR have in it?
Key Changes
Highlight the updates in specific files
Testing and Verification
How did you test these changes? What automated tests are added?
Related Issues
Jira tickets, GitHub issues, Support tickets...
PR Checklist