From 64c4487b8efd395b0c17fd33b4ba809fff5bd434 Mon Sep 17 00:00:00 2001
From: "Rodrigo Rodriguez (Pragmatismo)" <me@rodrigorodriguez.com>
Date: Sun, 25 Jan 2026 12:31:55 -0300
Subject: [PATCH] Fix CI recursive clone and document CI workflow strategy in
 PROMPT.md

---
 .forgejo/workflows/botserver.yaml |  2 +-
 PROMPT.md                         | 19 +++++++++++++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/.forgejo/workflows/botserver.yaml b/.forgejo/workflows/botserver.yaml
index 8101eca14..714f6b842 100644
--- a/.forgejo/workflows/botserver.yaml
+++ b/.forgejo/workflows/botserver.yaml
@@ -26,7 +26,7 @@ jobs:
 
       - name: Setup Workspace
         run: |
-          git clone https://alm.pragmatismo.com.br/GeneralBots/gb.git workspace
+          git clone --recursive https://alm.pragmatismo.com.br/GeneralBots/gb.git workspace
           rm -rf workspace/botserver
           mv botserver workspace/botserver
 
diff --git a/PROMPT.md b/PROMPT.md
index 9dcaf1f11..b7806af50 100644
--- a/PROMPT.md
+++ b/PROMPT.md
@@ -219,6 +219,25 @@ src/
 
 ---
 
+## 🚀 CI/CD WORKFLOW
+
+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.
+
+**Example Step:**
+```yaml
+- name: Setup Workspace
+  run: |
+    git clone --recursive https://alm.pragmatismo.com.br/GeneralBots/gb.git workspace
+    rm -rf workspace/botserver
+    mv botserver workspace/botserver
+```
+
+---
+
 ## 🔑 REMEMBER
 
 - **ZERO WARNINGS** - fix every clippy warning