fix cla workflow (#400)

orchestracities · Nov 20, 2020 · e4e8312 · e4e8312
1 parent d6395b6
commit e4e8312
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/.github/workflows/cla.yml b/.github/workflows/cla.yml
@@ -19,11 +19,11 @@ jobs:
           PERSONAL_ACCESS_TOKEN : ${{ secrets.PERSONAL_ACCESS_TOKEN }}
         with:
           path-to-signatures: 'signatures/version1/cla.json'
-          path-to-document: 'https://fiware.github.io/contribution-requirements/individual-cla.pdf' # e.g. a CLA or a DCO document
+          path-to-cla-document: 'https://fiware.github.io/contribution-requirements/individual-cla.pdf' # e.g. a CLA or a DCO document
           # branch should not be protected
           branch: 'cla-signature'
           allowlist: user1,bot*
-          use-dco-flag: false #'Set this to true if you want to use a dco instead of a cla'
+          # use-dco-flag: false #'Set this to true if you want to use a dco instead of a cla'
 
          #below 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)