From 222b9a8e6c36c7dc9fb3a287c0106a2cd5182674 Mon Sep 17 00:00:00 2001
From: "Rodrigo Rodriguez (Pragmatismo)" <me@rodrigorodriguez.com>
Date: Sun, 25 Jan 2026 14:17:11 -0300
Subject: [PATCH] docs(ci): update dev guide with minimal checkout strategy

---
 PROMPT.md | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/PROMPT.md b/PROMPT.md
index 2c9706cd1..c6c6886d7 100644
--- a/PROMPT.md
+++ b/PROMPT.md
@@ -223,15 +223,22 @@ src/
 
 When configuring CI/CD pipelines (e.g., Forgejo Actions):
 
-1.  **Clone the Full Workspace**: You MUST clone the entire `GeneralBots/gb` workspace recursively.
-2.  **Integrate BotServer**: Replace the `botserver` directory in the cloned workspace with the current CI checkout.
-3.  **Build in Context**: Run cargo commands from the workspace root (e.g., `cargo build -p botserver`) to ensure all workspace dependencies (like `botlib`, `botapp`) are correctly resolved.
+- **Minimal Checkout**: Clone only the root `gb` and the `botlib` submodule. Do NOT recursively clone everything.
+- **BotServer Context**: Replace the empty `botserver` directory with the current set of files being tested.
 
 **Example Step:**
 ```yaml
 - name: Setup Workspace
   run: |
-    git clone --depth 1 --recursive https://alm.pragmatismo.com.br/GeneralBots/gb.git workspace
+    # 1. Clone only the root workspace configuration
+    git clone --depth 1 https://alm.pragmatismo.com.br/GeneralBots/gb.git workspace
+    
+    # 2. Setup only the necessary dependencies (botlib)
+    cd workspace
+    git submodule update --init --depth 1 botlib
+    cd ..
+
+    # 3. Inject current BotServer code
     rm -rf workspace/botserver
     mv botserver workspace/botserver
 ```