Files
werkregie/doc/prs/2026-10-14-PR#82-author-message.md
claude-code c7dbb6b4c2
werkator build succeeded after 01:28
werkator/deploy build succeeded after 00:38
The message for a conflict leaves the version to the workflow (#82)
Co-authored-by: claude-code <claude-code@javagil.de>
2026-10-14 20:53:53 +02:00

49 lines
1.8 KiB
Markdown

# PR#82: The Message for a Conflict Leaves the Version to the Workflow
Version: patch
> **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.
## Related Links
- [werkregie PR#79](https://git.javagil.de/mi/werkregie/pulls/79), after which the build of werkregie derives the version.
- [werkregie PR#74](https://git.javagil.de/mi/werkregie/pulls/74), which added the message to copy.
## Problem
For a pull request in conflict, "Du bist dran" offers a message to the author session:
"bitte auf main rebasen, die nächste freie Version nehmen und pushen".
Since werkregie PR#79, werkregie derives its version, and a next free version would bring the conflict back.
The other Werk repositories still raise the version by hand, until they take the rule.
## Non-Goals
- No knowledge per repository of which rule it follows; the agentic workflow of the repository says it.
## Specification
### Feature: the message for a conflict leaves the version to the workflow
#### Scenario#82.01: the message names the workflow instead of a next free version
&hellip; so that the author session follows the rule of its repository.
- **Given** a pull request of an agent in conflict with `main`, with a known author session
- **When** "Du bist dran" shows it
- **Then** the message to copy asks to rebase onto `main`, check the version according to the workflow, and push
##### Verified by
- [AuthorsTest](../../dashboard/src/test/kotlin/de/hoennig/werkregie/dashboard/AuthorsTest.kt)
- [DemoTest](../../dashboard/src/test/kotlin/de/hoennig/werkregie/dashboard/DemoTest.kt)
## Solution
- `Authors.kt`: "bitte auf main rebasen, die Version nach dem Workflow prüfen und pushen".
## Open Questions
None.