Modify GitHub Actions workflow for documentation updates

Author: youssefea

.github/workflows/main.yml

@@ -17,6 +17,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
+          ref: ${{ github.head_ref }}  # Checkout the PR branch directly
 
       - name: Install Cursor CLI
         run: |
@@ -56,38 +57,38 @@ jobs:
       - name: Update docs for changed subdirectories
         if: steps.detect-changes.outputs.changed_subdirs != ''
         env:
-          MODEL: gpt-5
+          MODEL: gpt-4o
           CURSOR_API_KEY: ${{ secrets.CURSOR_API_KEY }}
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          BRANCH_PREFIX: docs
           CHANGED_SUBDIRS: ${{ steps.detect-changes.outputs.changed_subdirs }}
         run: |
           cursor-agent -p "You are operating in a GitHub Actions runner to update documentation summary files.
 
-          The GitHub CLI is available as \`gh\` and authenticated via \`GH_TOKEN\`. Git is available. You have write access to repository contents and can comment on pull requests, but you must not create or edit PRs.
+          The GitHub CLI is available as \`gh\` and authenticated via \`GH_TOKEN\`. Git is available. You have write access to repository contents and can comment on pull requests.
 
           # Context:
           - Repo: ${{ github.repository }}
           - Owner: ${{ github.repository_owner }}
           - PR Number: ${{ github.event.pull_request.number }}
           - Base Ref: ${{ github.base_ref }}
           - Head Ref: ${{ github.head_ref }}
-          - Docs Branch Prefix: ${{ env.BRANCH_PREFIX }}
           - Changed Subdirectories: $CHANGED_SUBDIRS
+          - Current Branch: ${{ github.head_ref }} (you are already on the PR branch)
 
           # Goal:
-          Update the llms.txt and llms-full.txt files in the changed subdirectories based on the content changes in those subdirectories.
+          Update the llms.txt and llms-full.txt files in the changed subdirectories and commit directly to the current PR branch.
 
           # Requirements:
-          1) For each subdirectory in CHANGED_SUBDIRS, analyze what changed in that subdirectory since the last commit.
+          1) For each subdirectory in CHANGED_SUBDIRS, analyze what changed in that subdirectory since the base branch.
           2) Update ONLY the llms.txt and llms-full.txt files in those specific subdirectories (e.g., docs/base-account/llms.txt, docs/base-account/llms-full.txt).
           3) DO NOT update the root-level llms.txt or llms-full.txt files.
           4) The llms.txt should be a concise summary/index of the documentation in that subdirectory.
           5) The llms-full.txt should be a comprehensive guide with code examples and detailed explanations.
           6) Maintain the existing format and style of these files.
-          7) Create or update a persistent docs branch for this PR using the Docs Branch Prefix.
-          8) Push changes to origin.
-          9) Post or update a single PR comment explaining what was updated with an inline compare link.
+          7) ONLY commit and push changes if there are actual updates needed to the llms files.
+          8) If no updates are needed, do NOT create any commits or comments.
+          9) Commit directly to the current PR branch (${{ github.head_ref }}) - do NOT create separate branches.
+          10) If you make changes, add a simple comment to the PR explaining what was updated.
 
           # File Structure Context:
           Each subdirectory (base-account, base-app, base-chain, cookbook, get-started, learn, mini-apps, onchainkit) contains:
@@ -96,15 +97,21 @@ jobs:
           - An llms-full.txt file (comprehensive guide with code examples)
 
           # Instructions:
-          1) Use \`gh pr diff\` to see what changed in the PR for the specific subdirectories.
+          1) Use \`gh pr diff ${{ github.event.pull_request.number }}\` to see what changed in the PR for the specific subdirectories.
           2) Read the current llms.txt and llms-full.txt files in each changed subdirectory.
           3) Scan the .mdx files in each changed subdirectory to understand the content.
-          4) Update the llms.txt and llms-full.txt files to reflect any new content, changes, or reorganization.
-          5) Ensure the updates are accurate and maintain the existing style.
-          6) Only make changes if documentation updates are actually needed.
-
-          # Deliverables when updates occur:
-          - Updated llms.txt and llms-full.txt files in the relevant subdirectories
-          - Pushed commits to the persistent docs branch
-          - A PR comment with inline compare link for easy PR creation
+          4) Update the llms.txt and llms-full.txt files ONLY if the changes warrant updates to the summaries.
+          5) If you make updates, commit them with a clear message like 'docs: update llms summaries for [subdirectory]'.
+          6) Push the commit to the current branch.
+          7) Add a brief comment to the PR explaining what was updated.
+          8) If no updates are needed, do nothing - no commits, no comments, no branches.
+
+          # Important: Avoid Getting Stuck
+          - If there are no changes to make, simply exit without doing anything.
+          - Do not create empty commits or branches.
+          - Do not post comments if no changes were made.
+
+          # Workflow:
+          1. Check what changed → 2. Determine if llms files need updates → 3. If yes: update, commit, push, comment → 4. If no: do nothing and exit
+
           " --force --model "$MODEL" --output-format=text