Fix CI recursive clone and document CI workflow strategy in PROMPT.md
This commit is contained in:
parent
fe8579e7b2
commit
64c4487b8e
2 changed files with 20 additions and 1 deletions
|
|
@ -26,7 +26,7 @@ jobs:
|
||||||
|
|
||||||
- name: Setup Workspace
|
- name: Setup Workspace
|
||||||
run: |
|
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
|
rm -rf workspace/botserver
|
||||||
mv botserver workspace/botserver
|
mv botserver workspace/botserver
|
||||||
|
|
||||||
|
|
|
||||||
19
PROMPT.md
19
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
|
## 🔑 REMEMBER
|
||||||
|
|
||||||
- **ZERO WARNINGS** - fix every clippy warning
|
- **ZERO WARNINGS** - fix every clippy warning
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue