GeneralBots/botserver
2
1
Fork 0
Code Issues Pull requests Projects Releases 323 Packages Wiki Activity Actions

docs(ci): update dev guide with minimal checkout strategy

Browse source
This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-01-25 14:17:11 -03:00
parent c5f8ea70cc
commit 222b9a8e6c
1 changed files with 11 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
PROMPT.md
View file

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