f700c33a1b
This fixes the issue where agents-llama containers were using the main FORGE_TOKEN (dev-bot) instead of dedicated credentials for the llama bot user. Changes: - forge-setup.sh: Added generation of FORGE_TOKEN_LLAMA and FORGE_PASS_LLAMA for local-model bot users (dev-qwen, dev-qwen-nightly). These are created as Forgejo users with their own API tokens and passwords for git push. - generators.sh: Updated agents-llama service to use FORGE_TOKEN_LLAMA and FORGE_PASS_LLAMA instead of falling back to dev-bot's credentials. Fixed escaping to defer variable resolution to docker-compose runtime. - docker-compose.yml: Updated to use FORGE_TOKEN_LLAMA and FORGE_PASS_LLAMA (renamed from FORGE_TOKEN_DEVQWEN for consistency). - .env.example: Added documentation for all per-bot tokens and passwords. - projects/disinto.toml.example: Documented the auto-credential generation. When a project TOML configures [agents.llama] with forge_user = dev-qwen: 1. disinto init creates the dev-qwen Forgejo user 2. Generates FORGE_TOKEN_LLAMA and FORGE_PASS_LLAMA 3. Adds dev-qwen as write collaborator on the project repo 4. The agents-llama container uses these credentials for all Forgejo API calls This ensures issues and PRs created by the llama agent are correctly attributed to dev-qwen instead of dev-bot. |
||
|---|---|---|
| .. | ||
| disinto.toml.example | ||
| harb.toml.example | ||
| versi.toml.example | ||