From 4a9a08b81d355401c469f27bdd074b1fdc8ecc52 Mon Sep 17 00:00:00 2001
From: Mac Siri <mac@forem.com>
Date: Wed, 15 Nov 2023 13:38:29 -0500
Subject: [PATCH] [CI] Make CLAAssistant reusable (#20359)

---
 .github/workflows/cla.yml | 17 +++--------------
 1 file changed, 3 insertions(+), 14 deletions(-)

diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml
index 7cf670ac9..544306a09 100644
--- a/.github/workflows/cla.yml
+++ b/.github/workflows/cla.yml
@@ -7,6 +7,7 @@ on:
   merge_group:
     branches:
       - main
+  workflow_call:
 
 permissions:
   actions: write
@@ -19,27 +20,15 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: "CLA Assistant"
-        if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'
+        if: ((github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target') && github.repository_owner == 'forem'
         uses: contributor-assistant/github-action@v2.3.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # the below token should have repo scope and must be manually added by you in the repository's secret
-          # This token is required only if you have configured to store the signatures in a remote repository/organization
           PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_PERSONAL_ACCESS_TOKEN }}
         with:
           path-to-signatures: 'signatures/version1/cla.json'
           path-to-document: 'https://github.com/forem/forem/blob/main/CLA.md'
-          # branch should not be protected
-          branch: 'main'
+          branch: 'main' # branch should not be protected
           allowlist: ${{ secrets.CLA_ALLOWLIST }}
-
-         # the followings are the optional inputs - If the optional inputs are not given, then default values will be taken
-          #remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)
           remote-repository-name: ${{ secrets.CLA_REPOSITORY }}
-          #create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
-          #signed-commit-message: 'For example: $contributorName has signed the CLA in $owner/$repo#$pullRequestNo'
-          #custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
-          #custom-pr-sign-comment: 'The signature to be committed in order to sign the CLA'
-          #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.'
           lock-pullrequest-aftermerge: false
-          #use-dco-flag: true - If you are using DCO instead of CLA