Skip to content

fix: Target correct branch within CLA workflow #975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2025
Merged

fix: Target correct branch within CLA workflow #975

merged 1 commit into from
Mar 24, 2025

Conversation

alessfg
Copy link
Member

@alessfg alessfg commented Mar 24, 2025

Proposed changes

The CLA implementation in #970 was targeting the wrong branch in the signature data store. This PR fixes the issue.

Checklist

Before creating a PR, run through this checklist and mark each as complete:

  • I have read the contributing guidelines
  • I have signed the F5 Contributor License Agreement (CLA)
  • I have run ./update.sh and ensured all entrypoint/Dockerfile template changes have been applied to the relevant image entrypoint scripts & Dockerfiles
  • If applicable, I have added tests that prove my fix is effective or that my feature works
  • If applicable, I have checked that any relevant tests pass after adding my changes
  • I have updated any relevant documentation (README.md and/or modules/README.md)

Copy link

github-actions bot commented Mar 24, 2025

✅ All required contributors have signed the F5 CLA for this PR. Thank you!
Posted by the CLA Assistant Lite bot.

@alessfg alessfg self-assigned this Mar 24, 2025
@alessfg alessfg requested a review from thresheek March 24, 2025 19:37
@alessfg alessfg added the bug label Mar 24, 2025
@thresheek thresheek merged commit d797950 into master Mar 24, 2025
18 of 19 checks passed
@alessfg alessfg deleted the fix-cla branch March 24, 2025 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants