Fix CI recursive clone and document CI workflow strategy in PROMPT.md

This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-01-25 12:31:55 -03:00
parent fe8579e7b2
commit 64c4487b8e
2 changed files with 20 additions and 1 deletions

View file

@ -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

View file

@ -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