Fix CLA bot

Change-Id: I6171c4d187c89ceda1fd928ad94ff475599f2dbb GitOrigin-RevId: eb48a79abde801e1986096fb59bcc2874ee75428
theashishmaurya · Dec 1, 2023 · 7b23c28 · 7b23c28
1 parent 8e98159
commit 7b23c28
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/.github/workflows/cla.yaml b/.github/workflows/cla.yaml
@@ -4,7 +4,7 @@ on:
     types: [created]
   pull_request_target:
     types: [opened,closed,synchronize]
-    paths: ['studio/**']
+    paths: ['platform/**']
 
 jobs:
   CLAAssistant:
@@ -21,7 +21,7 @@ jobs:
           path-to-document: 'https://github.com/plasmicapp/plasmic/blob/master/docs/contributing/individual-cla.md' # e.g. a CLA or a DCO document
           # branch should not be protected
           branch: 'master'
-          allowlist: user1,bot*
+#          allowlist: user1,bot*
 
          # 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)