ci: add gh action workflow definition for F5 CLA automation #661
Conversation
TasoOneAsia
added
the
github_actions
|
@lucacome Should this get any additional reviews, or is this good to go? |
|
@TasoOneAsia we require two approvals |
|
Should this PR update the contributing guide to advise how to get approval for the F5 CLA? |
|
@pdabelf5 Good call 👍 I'll update |
github-actions
bot
added
documentation
TasoOneAsia
force-pushed
the
ci/cla-automation
branch
from
688dcd2 to
4d408bc
Compare
|
Since this got the two approvals, I'll go ahead and squash + merge this on Monday if there are no objections. |
|
@TasoOneAsia what is the status of this? |
| remote-repository-name: 'f5-cla-data' | ||
| path-to-signatures: 'signatures/beta/signatures.json' | ||
| # Comma seperated list of usernames for maintainers or any other individuals who should not be prompted for a CLA. | ||
| allowlist: Dean-Coakley, pleshakov, lucacome, bot* |
There was a problem hiding this comment.
Not sure if former employees need to sign the CLA or not, but we should probably remove Dean.
|
I'm going to close this since it's been open for 3+ months and there's no activity. Feel free to re-open it. |
|
@lucacome Sorry about the delay in circling back to this, I'll update the branch to reflect a couple small changes that were made to the workflow recently and open up a new PR. |
|
sounds good @TasoOneAsia thanks! |
Proposed changes
Adds a GH action workflow file (
.github/workflows/f5-cla.yml) for F5 contributor license agreement (CLA) automation and compliance. This action is configured to target a shared signature store for F5 Open Source projects and will prompt contributors, upon pull request tomain, to sign the F5 CLA if they have not already done so.As part of the configuration for this project, the following GitHub usernames were whitelisted as maintainers:
Dean-CoakleypleshakovlucacomeChecklist
Before creating a PR, run through this checklist and mark each as complete.
guide