mhoennigandClaude Opus 5.5
04461a274a
[engine] mode chooses the review: "llm" (default, unchanged), "classifier" (Jev alone, no LLM) or "combined" (Jev, then the LLM with Jev's flagged units as hints in the user prompt). werkrevisor splits each changed PR document into ##/### sections and #### Scenario units, asks Jev once per unit with the operator's questions, and maps every answer to a problem value: each question asks for a problem, a score runs from "no problem" to "worst problem". A clear spec problem is RED, a doubtful one or an oversized unit YELLOW, a Jev error ERROR. The hints carry file, line, scenario id, question and value, but no PR text. tools/jev-eval measures the questions offline on local PR documents. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
43 lines
1018 B
Markdown
43 lines
1018 B
Markdown
# PR#901: build status badge
|
|
|
|
## The Problem
|
|
|
|
A README cannot show whether the latest build of a branch is green.
|
|
|
|
## The Scenarios
|
|
|
|
### Feature: status badge per branch
|
|
|
|
#### Scenario#901.01: The badge of a green branch is green
|
|
|
|
So that a README shows the build state at a glance.
|
|
|
|
- **Given** a branch `main` whose latest build succeeded
|
|
- **When** `GET /branches/main/badge.svg` is requested
|
|
- **Then** a green SVG badge is served
|
|
- **and** it is served with `no-store` cache headers.
|
|
|
|
##### Verified by
|
|
|
|
- [BadgeControllerTest](../../src/test/kotlin/BadgeControllerTest.kt)
|
|
|
|
### Feature: badges for unknown branches
|
|
|
|
#### Scenario#901.02: An unknown branch gets a grey badge
|
|
|
|
- **Given** no branch `nope`
|
|
- **When** `GET /branches/nope/badge.svg` is requested
|
|
- **Then** a grey badge with the text "unknown" is served
|
|
|
|
##### Verified by
|
|
|
|
- [BadgeControllerTest](../../src/test/kotlin/BadgeControllerTest.kt)
|
|
|
|
## The Solution
|
|
|
|
~~~markdown
|
|
### Feature: inside a tilde fence
|
|
~~~
|
|
|
|
A new controller renders the SVG.
|