chore: add piloop-config.yaml #151

Merged

david merged 1 commit from chore/2026-09-01/piloop-config into main

2026-08-31 23:16:11 +00:00

david commented

2026-08-31 23:04:09 +00:00

Owner

Adds a committed per-repo piloop-config.yaml for pi-loop, copied from the annotated example so stable team settings are shared via PR review instead of local only.

What & why
pi-loop supports an optional per-repo YAML config at the repo root. Committing it makes the team's shared settings explicit and reviewable (precedence: CLI flag > env var > YAML > built-in defaults). The file pins:

git-host: forgejo — origin platform for MR creation
label: enhancement — scan-mode label filter
model: deepseek-v4-flash + thinking-level: high
auto-merge enabled with default timeout/poll
bash timeout bounds, Jira/GitLab/Forgejo settings, docs-sync stage defaults

Credentials/tokens are intentionally not in this file — they stay in the environment.

Per-file breakdown

Added: piloop-config.yaml — annotated per-repo pi-loop configuration (82 lines)

Adds a committed per-repo `piloop-config.yaml` for pi-loop, copied from the annotated example so stable team settings are shared via PR review instead of local only. **What & why** pi-loop supports an optional per-repo YAML config at the repo root. Committing it makes the team's shared settings explicit and reviewable (precedence: CLI flag > env var > YAML > built-in defaults). The file pins: - `git-host: forgejo` — origin platform for MR creation - `label: enhancement` — scan-mode label filter - `model: deepseek-v4-flash` + `thinking-level: high` - `auto-merge` enabled with default timeout/poll - bash timeout bounds, Jira/GitLab/Forgejo settings, docs-sync stage defaults Credentials/tokens are intentionally **not** in this file — they stay in the environment. **Per-file breakdown** - **Added:** `piloop-config.yaml` — annotated per-repo pi-loop configuration (82 lines)

david added the

chore

label

2026-08-31 23:04:09 +00:00

david added 1 commit

2026-08-31 23:04:09 +00:00