Answer: The Cline GitHub Actions integration works via the `cline-responder.yml` workflow, which triggers on issue comments mentioning `@cline`, verifies the commenter can write to the repository, installs Cline CLI globally with npm, configures authentication, runs `git-scripts/analyze-issue.sh` in yolo mode with auto-approval, and posts the analysis as a comment from a separate job that doesn't run Cline. Status: Confirmed Entry: tool/cline/agents-and-automation/how-github-actions-integration-works Revision: 1 Digest: sha256:675081683efaa750 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:06:22Z Last changed: 2026-11-13T03:06:22Z Last verified: 2026-11-20T12:26:59Z Next check: 2026-11-21T12:26:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of workflow file | cline-responder.yml | [1] | 2026-11-20 trigger | @cline | [1] | 2026-11-20 author check | can write to the repository | [1] | 2026-11-20 install method | npm | [1] | 2026-11-20 auth command | cline auth --provider openrouter --apikey ... --modelid ... | [1] | 2026-11-20 analysis script | git-scripts/analyze-issue.sh | [1] | 2026-11-20 posting job | a separate job that doesn't run Cline | [1] | 2026-11-20 Sources: [1] Cline. "GitHub Actions Integration". https://docs.cline.bot/cli/samples/github-integration.md Role: primary. Accessed: 2026-11-20T12:26:59Z Quote: "The workflow (`cline-responder.yml`):" (Supports: workflow file) Quote: "**Triggers** on issue comments (created or edited) that mention `@cline`" (Supports: trigger) Quote: "**Checks** that the comment's author can write to the repository" (Supports: author check) Quote: "**Installs** Cline CLI globally using npm" (Supports: install method) Quote: "**Configures** authentication using `cline auth --provider openrouter --apikey ... --modelid ...`" (Supports: auth command) Quote: "**Runs** `git-scripts/analyze-issue.sh` from your repository, which runs Cline in yolo mode with auto-approval" (Supports: analysis script) Quote: "**Posts** the analysis as a comment, from a separate job that doesn't run Cline" (Supports: posting job) Published: 2026-11-20T05:59:41Z Snapshot SHA-256: 3e56ebd5a81b7a76fa9ddf1a21a362b3dcb9f7a5b26d89514b899b1f3fa61be9 (captured 2026-11-13T03:06:22Z) 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-13T03:06:22Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:26:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:26:59Z Last attempt: 2026-11-20T12:26:59Z Notes and limitations: Extracted automatically from a single official source (section "How It Works"). Related: https://latestn.com/tool/cline/agents-and-automation/hub-spoke-roles What are the hub, spoke, and client roles in Cline's hub-spoke architecture? https://latestn.com/tool/cline/agents-and-automation/link-tasks-dependency-chain How do I link tasks together in Cline Kanban so the next task starts automatically? https://latestn.com/tool/cline/agents-and-automation/manage-schedules How do I manage, pause, or delete existing Cline schedules? https://latestn.com/tool/cline/agents-and-automation/enable-multi-agent-teams How do I enable multi-agent teams in Cline? https://latestn.com/tool/cline/agents-and-automation/event-streaming How do I stream events from a Cline SDK agent run? https://latestn.com/tool/cline/agents-and-automation/handle-tool-errors How do I handle tool errors in Cline agents so the agent can recover? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:06:22Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/agents-and-automation/how-github-actions-integration-works/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/agents-and-automation/how-github-actions-integration-works POST: https://latestn.com/dispute/tool/cline/agents-and-automation/how-github-actions-integration-works with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/agents-and-automation/how-github-actions-integration-works?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does the Cline GitHub Actions integration work under the hood? Revision 1, last verified 2026-11-20T12:26:59Z. https://latestn.com/tool/cline/agents-and-automation/how-github-actions-integration-works (accessed 2026-11-21T10:03:57Z). @misc{LatestN_tool_cline_agents_and_automation_how_github_actions_integration_works_r1, title = {How does the Cline GitHub Actions integration work under the hood?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/agents-and-automation/how-github-actions-integration-works}}, note = {Revision 1; digest sha256:675081683efaa750; last verified 2026-11-20T12:26:59Z; accessed 2026-11-21T10:03:57Z} } 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/agents-and-automation/how-github-actions-integration-works