-
Notifications
You must be signed in to change notification settings - Fork 134
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
ci: adds a GH action workflow file for F5 CLA automation #224
Conversation
It just occured to me that we might want to update the contributing guide and PR template to note that F5 now requires a CLA. I'll work on it as soon as I get a chance. |
8079ed3
to
cdce8a3
Compare
cdce8a3
to
7351cbb
Compare
* add CLA to the PR template * mention CLA in the contributing guidelines
6d2bced
to
119c0e0
Compare
CLA Assistant Lite bot: 🎉 Thank you for your contribution. It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 project. Please kindly read the F5 CLA and comment the following to agree: I have hereby read the F5 CLA and agree to its terms 1 out of 2 committers have signed the CLA. |
Proposed Changes
Adds a GitHub action workflow file configured for F5 contributor license agreement automation and compliance. This action is configured to target a shared signature store for F5 Open Source projects. As part of the configuration, the following GitHub usernames were whitelisted as maintainers:
4141done
dekobon
Any contributors not included in this whitelist will be asked to review the F5 CLA upon a pull request to the
master
main
branch and to leave a comment agreeing to the terms before their contribution is merged.Let me know if there are any other questions :)