You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Review rules as a fork feature: finish the judge (C3, C4) and the lens tools (T3-T5) #888
What: review rules as a fork feature. A project's config says which review lenses a change needs (by changed path and tier), the merge gate judges it, and T3 tools start lenses, record their reports and arm the PR, so the rules are enforced by code and not by the orchestrator's memory.
Why the owner wants it: reviews decide whether unattended work is safe to merge; today much of it is prose rules and a project-specific gate.
Done when: every project's merge gate reads one review config from the fork, lenses are started and recorded by T3 tools, and a PR without its required lenses cannot merge.
Activity