Split Forgejo CI workflows and update documentation

CI/CD Improvements:
- Split monolithic botserver workflow into botserver-only and botui-only workflows
- BotServer CI: Triggers on botserver/**, botlib/** changes, builds only botserver
- BotUI CI: New workflow, triggers on botui/**, botlib/** changes, builds only botui
- Separate caches to avoid conflicts between projects
- Independent deployments and service restarts

Documentation:
- Remove WHATSAPP-CONFIG-GUIDE.md (duplicate of botbook documentation)
- Update README.md with new rule: check botbook/ before creating .md files
- Add workflow step to check existing documentation first

Submodule updates:
- botserver: Updated .forgejo/workflows/botserver.yaml (botserver-only)
- botui: Added .forgejo/workflows/botui.yaml (new botui workflow)
This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-02-05 08:45:41 -03:00
parent f97451482d
commit 090b42618b
3 changed files with 9 additions and 7 deletions

View file

@ -858,6 +858,7 @@ validate_table_name(&safe_table)?;
❌ NEVER modify Cargo.toml lints section! ❌ NEVER modify Cargo.toml lints section!
❌ NEVER use CDN links - all assets must be local ❌ NEVER use CDN links - all assets must be local
❌ NEVER use cargo clean - causes 30min rebuilds, use ./reset.sh for database issues ❌ NEVER use cargo clean - causes 30min rebuilds, use ./reset.sh for database issues
❌ NEVER create .md documentation files without checking botbook/ first - documentation belongs there
``` ```
--- ---
@ -1035,11 +1036,12 @@ Subprojects (botapp, botserver, etc.) are **not** git submodules - they are inde
## Development Workflow ## Development Workflow
1. Read this README.md (workspace-level rules) 1. Read this README.md (workspace-level rules)
2. Read `<project>/README.md` (project-specific rules) 2. **BEFORE creating any .md file, search botbook/ for existing documentation**
3. Use diagnostics tool to check warnings 3. Read `<project>/README.md` (project-specific rules)
4. Fix all warnings with full file rewrites 4. Use diagnostics tool to check warnings
5. Verify with diagnostics after each file 5. Fix all warnings with full file rewrites
6. Never suppress warnings with `#[allow()]` 6. Verify with diagnostics after each file
7. Never suppress warnings with `#[allow()]`
--- ---

@ -1 +1 @@
Subproject commit 64d5e2a1bd79cf34df02ec6f61d4dfdd5e1a3fe9 Subproject commit 30345c66e2738ebe73d896841e54f655999e3630

2
botui

@ -1 +1 @@
Subproject commit 91a750127c674b04858a8d59f21614538f71d1ee Subproject commit e0504f37030ffd8c4a33188df8daf5b83edc52e9