From d797950017665ebf75d77ace030deb2a021702d8 Mon Sep 17 00:00:00 2001
From: Alessandro Fael Garcia <alessfg@hotmail.com>
Date: Mon, 24 Mar 2025 20:36:14 +0100
Subject: [PATCH] fix: Target correct branch within CLA workflow
---
.github/workflows/f5_cla.yml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/.github/workflows/f5_cla.yml b/.github/workflows/f5_cla.yml
index 58e8117..43e473e 100644
--- a/.github/workflows/f5_cla.yml
+++ b/.github/workflows/f5_cla.yml
@@ -19,9 +19,6 @@ jobs:
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@ca4a40a7d1004f18d9960b404b97e5f30a505a08 # v2.6.1
with:
- # Any pull request targeting the following branch will trigger a CLA check.
- # NOTE: You might need to edit this value to 'main'.
- branch: master
# Path to the CLA document.
path-to-document: https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md
# Custom CLA messages.
@@ -31,6 +28,8 @@ jobs:
# Remote repository storing CLA signatures.
remote-organization-name: f5
remote-repository-name: f5-cla-data
+ # Branch where CLA signatures are stored.
+ branch: main
path-to-signatures: signatures/signatures.json
# Comma separated list of usernames for maintainers or any other individuals who should not be prompted for a CLA.
# NOTE: You will want to edit the usernames to suit your project needs.
--
GitLab