Files
werkrevisor/docs/prs/2026-10-11-PR#83-werkbaum-host.md
claude-code 9c09ef58fa
werkator build succeeded after 00:37
werkator/werkrevisor-statistics build succeeded after 00:56
werkrevisor reviews werkbaum (#83)
The host config for mi/werkbaum, with automerge.

See docs/prs/.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #83
Reviewed-by: ai-reviewer <2+ai-reviewer@noreply.git.javagil.de>
Co-authored-by: claude-code <claude-code@javagil.de>
2026-10-11 14:02:07 +02:00

1.6 KiB

PR#83: werkrevisor Reviews werkbaum

WARNING: This document describes only the change applied in this PR. It may already be outdated once the next PR is merged. Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.

Problem

werkbaum follows the shared agentic workflow since werkbaum PR#7, but has no review by werkrevisor. So no bot schedules the merge: an approved PR with a green CI stays open until the human merges it.

Non-Goals

  • No .werkrevisor.toml in werkbaum; werkbaum chooses its risk template in a PR of its own.
  • No branch protection, no collaborator, no Werkator build; the human sets them up on Gitea and mih09.

Solution

  • config/werkbaum.toml is the host config for mi/werkbaum, derived from that of werkregie, with require_wip_transition and automerge.
  • Its categories fit the monorepo: the editor under frontend/, the Spring Boot backend under backend/, tests under frontend/tests/ and backend/src/test/, the OpenAPI spec as api_spec.
  • Judged paths are the build, CI and deploy files: .github/**, .werkator*, scripts/**, tools/**, the Gradle and npm build files.
  • The PR documents are German; their open questions stand under "Offene Fragen".
  • The writing rules allow long lines and paragraphs: docs/CHANGELOG.md holds one note per line, and docs/DECISIONS.md argues in long paragraphs.
  • The tests of the example configs include it.
  • Version 0.32.10.