Repository navigation
chore: add cla gate - #2065
chore: add cla gate#2065
Conversation
|
@claude review |
There was a problem hiding this comment.
Claude Code Review
No review was started: this request came from a bot account. Manual reviews can only be requested by someone with write access to this repository. Ask a maintainer to comment @claude review, or have your automation post the comment from a user account with write access.
Tip: disable this comment in your organization's Code Review settings.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff71291df3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Beyond the inline findings, I checked two more things and found no problem. First, the workflow runs on pull_request_target, so I looked for script injection. It never checks out PR code, and the github-script body reads PR data through context.payload instead of ${{ }} interpolation. The only interpolation is in the concurrency group key. Second, listCommitStatusesForRef returns statuses newest first, so the find picks up the most recent license/cla status from that creator, not an old one.
Extended reasoning...
This adds one new GitHub Actions workflow on the pull_request_target, merge_group and status triggers. It publishes a commit status that is meant to become a required check, so it controls merge gating. This note only lists what was checked beyond the inline findings, which are left as they are.
Findings marked 🟡 are optional suggestions and need no follow-up push.


Confidence Score: 5/5
The PR appears safe to merge; no blocking issue was found.Summary
Adds a GitHub Actions workflow that publishes
CLA gatefor pull requests and the merge queue.CLA gatestatus based on contributor access or a signed CLA.Diagram
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Workflow event] --> B{Merge group?} B -->|Yes| C[Publish success] B -->|No| D[Find matching open PRs] D --> E{All contributors exempt?} E -->|Yes| C E -->|No| F{Trusted CLA status successful?} F -->|Yes| C F -->|No| G[Publish failure]Reviews (2) · Last reviewed commit: "chore: add cla gate" · Reviewed by Greptile