From e1cc98d448f8db971fc2fbed6055839b2f233d2f Mon Sep 17 00:00:00 2001
From: Aiden Cline <aidenpcline@gmail.com>
Date: Tue, 25 Nov 2025 23:51:23 -0600
Subject: Revert "feat(github): add ability to react to PR Review Comments in
 Workflow (#4705)"

This reverts commit 0ce64962d4c9eeaa7c9e4da84a4702f03927055a.
---
 packages/web/src/content/docs/github.mdx | 19 -------------------
 1 file changed, 19 deletions(-)

(limited to 'packages/web/src/content/docs/github.mdx')

diff --git a/packages/web/src/content/docs/github.mdx b/packages/web/src/content/docs/github.mdx
index 19c7782ef..359f696fc 100644
--- a/packages/web/src/content/docs/github.mdx
+++ b/packages/web/src/content/docs/github.mdx
@@ -45,8 +45,6 @@ Or you can set it up manually.
    on:
      issue_comment:
        types: [created]
-     pull_request_review_comment:
-       types: [created]
 
    jobs:
      opencode:
@@ -131,20 +129,3 @@ Here are some examples of how you can use opencode in GitHub.
   ```
 
   opencode will implement the requested change and commit it to the same PR.
-
-- **Review specific code lines**
-
-  Leave a comment directly on code lines in the PR's "Files" tab. opencode automatically detects the file, line numbers, and diff context to provide precise responses.
-
-  ```
-  [Comment on specific lines in Files tab]
-  /oc add error handling here
-  ```
-
-  When commenting on specific lines, opencode receives:
-  - The exact file being reviewed
-  - The specific lines of code
-  - The surrounding diff context
-  - Line number information
-
-  This allows for more targeted requests without needing to specify file paths or line numbers manually.
-- 
cgit v1.2.3

