Repository navigation
JGC-448 - Add explicit GITHUB_TOKEN permissions to CLA workflow - #3428
Merged
Merged
Conversation
Made-with: Cursor
RemiBou
added
the
safe to test
RemiBou
enabled auto-merge (squash)
April 13, 2026 11:15
cyrilc-pro
approved these changes
Apr 13, 2026
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns
jfrog-cliCLA Assistant workflow withjfrog-cli-core(see jfrog/jfrog-cli-core#1523). Tracks JGC-448.Problem
When workflow default
GITHUB_TOKENpermissions are read-only at org/repo level, the contributor-assistant action cannot comment on PRs or set commit statuses, so the CLA check fails.Changes
permissions(actions,contents,pull-requests,statuses).pull_request_targetto PRs targetingmaster.Supersedes #3427 (duplicate Jira ticket removed).