Our summary
An automated code check can keep raising a warning that a reviewer has already dismissed. Heather Downing saves that correction in Meko, a shared store of team knowledge, rather than teaching new behaviour inside Jev itself. An owner or maintainer must approve the saved ruling before the team can reuse it.
The program first asks Jev whether each block of changed code breaks a guideline, without adding past exceptions. For warnings that remain, it searches for relevant rulings and asks separately whether each one applies. A ruling names the rule, its scope and its reason; uncertain matches go to a person.
Yugabyte reports testing four blocks of changed code before and after one approved ruling, plus 21 labelled cases. These are small tests reported by the company, not checked by outsiders. An exception should remove only its intended warning. Stricter rules belong in the guidelines; code sent to Jev leaves the team.
Key takeaways
- Store a reviewer's correction outside the model and require approval before sharing it.
- Judge the rule first, then ask a separate, narrow question about any exception.
- Keep the ruling's scope and reason, record the decisions, and send uncertain matches to a person.