Manage Review Policies and Reviewer Profiles safely #21

Open
opened 2026-07-14 22:32:25 -04:00 by caleb-brown · 0 comments
Owner

What to build

Temper Operators can evolve review behavior across repositories with validated, explainable, immutable configuration revisions that never rewrite completed history.

Acceptance criteria

  • Operators can create, edit, disable, and inspect Reviewer Profiles and Repository Review Policies.
  • Matching, composition, precedence, manual overrides, thresholds, caps, and budgets are visible and validated.
  • Policy activation creates an immutable revision and clearly identifies which repositories will change.
  • Existing review requests retain their frozen configuration while later requests use the new active revision.
  • Deleting or disabling configuration cannot make historical Review Runs inexplicable.
  • Changes and activation are included in the Operator audit trail.
  • Tests cover multiple matches, defaults, invalid references, activation changes, and concurrent review requests.

Blocked by

  • #13 — Activate a repository Review Policy
  • #15 — Produce a bounded review result
## What to build Temper Operators can evolve review behavior across repositories with validated, explainable, immutable configuration revisions that never rewrite completed history. ## Acceptance criteria - [ ] Operators can create, edit, disable, and inspect Reviewer Profiles and Repository Review Policies. - [ ] Matching, composition, precedence, manual overrides, thresholds, caps, and budgets are visible and validated. - [ ] Policy activation creates an immutable revision and clearly identifies which repositories will change. - [ ] Existing review requests retain their frozen configuration while later requests use the new active revision. - [ ] Deleting or disabling configuration cannot make historical Review Runs inexplicable. - [ ] Changes and activation are included in the Operator audit trail. - [ ] Tests cover multiple matches, defaults, invalid references, activation changes, and concurrent review requests. ## Blocked by - [#13](https://git.caleb-brown.dev/caleb-brown/temper/issues/13) — Activate a repository Review Policy - [#15](https://git.caleb-brown.dev/caleb-brown/temper/issues/15) — Produce a bounded review result
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#21
No description provided.