doc: improve agentic workflow — CI wait, branch strategy, dependency rules for all agents
CI / lint (push) Successful in 8s
CI / sanitizers (address) (push) Successful in 15s
CI / build-and-test (push) Successful in 54s

This commit is contained in:
2026-07-20 14:22:16 +02:00
parent 02ceb6828b
commit d3b0cb9357
13 changed files with 166 additions and 10 deletions
+12
View File
@@ -153,3 +153,15 @@ Before and after each refactor, note:
- **Breaking the API** — public headers are contracts; change them carefully
- **Rewriting** — refactor incrementally, don't rewrite from scratch
- **Ignoring tests** — if tests don't exist for the code you're refactoring, write them first
## CI & Task Execution
When using `tea` (the task execution agent) to run CI or tests, always set a sufficient timeout (e.g., 600000ms) to allow the workflow to finish. After CI completes, check the results yourself — inspect logs if the run failed. Never assume success.
## Branch Strategy
Never push directly to `main`. All changes must be developed on a feature branch and merged via a pull request. Always create a new branch (`git checkout -b <branch-name>`) before making changes, push it, and open a PR with `gh pr create --fill`. Wait for CI to pass before merging.
## Dependency Installation
All dependencies must be installed via the project's custom Docker image (repo-root `Dockerfile`, same image CI uses) — never via ad-hoc host package installs (no `apt-get install` / `pip install` on the host machine). See `AGENTS.md` for details.