From 45d5b6f6c88206e7418f0202b896861fe1b1425f Mon Sep 17 00:00:00 2001
From: Luca Comellini <luca.com@gmail.com>
Date: Fri, 6 Sep 2024 13:03:30 -0700
Subject: [PATCH] Use CLA GitHub Action

---
 .github/workflows/f5-cla.yml | 51 ++++++++++++++++++++++++++++++++++++
 .yamllint.yaml               |  4 ---
 CONTRIBUTING.md              | 10 +++++++
 3 files changed, 61 insertions(+), 4 deletions(-)
 create mode 100644 .github/workflows/f5-cla.yml

diff --git a/.github/workflows/f5-cla.yml b/.github/workflows/f5-cla.yml
new file mode 100644
index 00000000..de0dbc8a
--- /dev/null
+++ b/.github/workflows/f5-cla.yml
@@ -0,0 +1,51 @@
+name: F5 CLA
+
+on:
+  issue_comment:
+    types:
+      - created
+  pull_request_target:
+    types:
+      - opened
+      - synchronize
+      - reopened
+
+concurrency:
+  group: ${{ github.ref_name }}-cla
+
+permissions:
+  contents: read
+
+jobs:
+  f5-cla:
+    name: F5 CLA
+    runs-on: ubuntu-22.04
+    permissions:
+      actions: write
+      contents: read
+      pull-requests: write
+      statuses: write
+    steps:
+      - name: Run F5 Contributor License Agreement (CLA) assistant
+        if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have hereby read the F5 CLA and agree to its terms') || github.event_name == 'pull_request_target'
+        uses: contributor-assistant/github-action@f41946747f85d28e9a738f4f38dbcc74b69c7e0e # v2.5.1
+        with:
+          # Any pull request targeting the following branch will trigger a CLA check.
+          branch: "main"
+          # Path to the CLA document.
+          path-to-document: "https://github.com/f5/.github/blob/main/CLA/cla-markdown.md"
+          # Custom CLA messages.
+          custom-notsigned-prcomment: "🎉 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 Open Source Software (OSS) project. Please kindly read the [F5 CLA](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md) and reply on a new comment with the following text to agree:"
+          custom-pr-sign-comment: "I have hereby read the F5 CLA and agree to its terms"
+          custom-allsigned-prcomment: "✅ All required contributors have signed the F5 CLA for this PR. Thank you!"
+          # Remote repository storing CLA signatures.
+          remote-organization-name: "f5"
+          remote-repository-name: "f5-cla-data"
+          path-to-signatures: "signatures/beta/signatures.json"
+          # Comma separated list of usernames for maintainers or any other individuals who should not be prompted for a CLA.
+          allowlist: bot*
+          # Do not lock PRs after a merge.
+          lock-pullrequest-aftermerge: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PERSONAL_ACCESS_TOKEN: ${{ secrets.F5_CLA_TOKEN }}
diff --git a/.yamllint.yaml b/.yamllint.yaml
index 7d0320c4..dd2afab7 100644
--- a/.yamllint.yaml
+++ b/.yamllint.yaml
@@ -1,8 +1,4 @@
 ---
-yaml-files:
-  - "*.yaml"
-  - "*.yml"
-
 ignore-from-file: .gitignore
 
 extends: default
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d11a7a6e..ce4f0c67 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -14,6 +14,7 @@ considering contributing!
   - [Suggest an Enhancement](#suggest-an-enhancement)
   - [Open a Pull Request](#open-a-pull-request)
   - [Issue lifecycle](#issue-lifecycle)
+  - [F5 Contributor License Agreement (CLA)](#f5-contributor-license-agreement-cla)
 - [Style Guides](#style-guides)
   - [Git Style Guide](#git-style-guide)
   - [Go Style Guide](#go-style-guide)
@@ -60,6 +61,15 @@ issue template.
   type of issue it is (bug, feature request, etc) and to determine the milestone. Please see the [Issue
   Lifecycle](ISSUE_LIFECYCLE.md) document for more information.
 
+### F5 Contributor License Agreement (CLA)
+
+F5 requires all external contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md))
+before any of their changes can be incorporated into an F5 Open Source repository.
+
+If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and
+agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes
+can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs.
+
 ## Style Guides
 
 ### Git Style Guide