Define Temper's developer-facing review contract #30
Labels
No labels
ready-for-agent
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#35 Define revision, trigger, deduplication, retry, and stale-run semantics
caleb-brown/temper
#37 Define Review Policy and Reviewer Profile semantics
caleb-brown/temper
#39 Prototype the Forgejo review presentation and feedback lifecycle
caleb-brown/temper
#41 Define the durable domain and audit model
caleb-brown/temper
Reference
caleb-brown/temper#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#29 — Temper v1 Greenfield Product and Architecture
Question
What exactly does Temper promise developers inside Forgejo: which pull-request events and explicit controls request a review, which summary, inline, and status effects appear, what advisory review means, and how those effects evolve across revisions, reruns, partial coverage, failures, and no-findings outcomes?
Blocked by