Answer: The workflow skips pull requests from forks because GitHub doesn't pass secrets to those workflows, and it warns not to switch to `pull_request_target`. To review a fork pull request, you read it first, then run the workflow from the Actions tab and enter the pull request's number. Status: Confirmed Entry: tool/cline/permissions-and-security/fork-pr-handling Revision: 1 Digest: sha256:eeb785ede7c7d714 (changes whenever the content changes) Timeline: Created: 2026-11-15T12:27:30Z Last changed: 2026-11-15T12:27:30Z Last verified: 2026-11-20T12:27:05Z Next check: 2026-11-21T12:27:05Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of handling | The workflow skips those pull requests. | [1] | 2026-11-20 reason | GitHub doesn't pass your secrets to workflows run for pull requests from forks or from Dependabot | [1] | 2026-11-20 warning | Don't switch to `pull_request_target` to review them automatically | [1] | 2026-11-20 manual review method | run the workflow from the **Actions** tab and enter the pull request's number | [1] | 2026-11-20 Sources: [1] Cline. "GitHub PR Review". https://docs.cline.bot/cli/samples/github-pr-review.md Role: primary. Accessed: 2026-11-20T12:27:05Z Quote: "The workflow skips those pull requests." (Supports: handling) Quote: "GitHub doesn't pass your secrets to workflows run for pull requests from forks or from Dependabot" (Supports: reason) Quote: "Don't switch to `pull_request_target` to review them automatically" (Supports: warning) Quote: "run the workflow from the **Actions** tab and enter the pull request's number" (Supports: manual review method) Published: 2026-11-20T05:59:42Z Snapshot SHA-256: 72b1a90b762b54b899242749c91b229730dbd2e3f4ae295675c63c1ce96aa4b0 (captured 2026-11-13T03:06:24Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T12:27:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:27:05Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:27:05Z Last attempt: 2026-11-20T12:27:05Z Notes and limitations: Extracted automatically from a single official source (section "Pull Requests from Forks"). Related: https://latestn.com/tool/cline/permissions-and-security/openai-compatible-security-practices What security best practices should I follow when using an OpenAI-compatible endpoint with Cline? https://latestn.com/tool/cline/permissions-and-security/policy-options What policy options exist for Cline tools (autoApprove true/false, enabled false, default)? https://latestn.com/tool/cline/permissions-and-security/pr-review-permissions-secrets What permissions and secrets are required for Cline's GitHub PR review workflow? https://latestn.com/tool/cline/permissions-and-security/enforce-clineignore-with-hook How do I enforce .clineignore rules with a hook in Cline? https://latestn.com/tool/cline/permissions-and-security/enterprise-api-authentication How do I authenticate requests to the Cline Enterprise API? https://latestn.com/tool/cline/permissions-and-security/enterprise-permissions-matrix What permissions does each Cline Enterprise role have? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T12:27:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/permissions-and-security/fork-pr-handling/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/permissions-and-security/fork-pr-handling POST: https://latestn.com/dispute/tool/cline/permissions-and-security/fork-pr-handling with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/permissions-and-security/fork-pr-handling?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does Cline handle pull requests from forks in the GitHub PR review workflow? Revision 1, last verified 2026-11-20T12:27:05Z. https://latestn.com/tool/cline/permissions-and-security/fork-pr-handling (accessed 2026-11-21T10:07:11Z). @misc{LatestN_tool_cline_permissions_and_security_fork_pr_handling_r1, title = {How does Cline handle pull requests from forks in the GitHub PR review workflow?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/permissions-and-security/fork-pr-handling}}, note = {Revision 1; digest sha256:eeb785ede7c7d714; last verified 2026-11-20T12:27:05Z; accessed 2026-11-21T10:07:11Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/permissions-and-security/fork-pr-handling