inline

House rules that earn their place

A learning is one rule, in a sentence, that inline applies to future reviews. Your team can teach one from any pull request, and inline drafts them from what the team keeps dismissing or fixing. Every rule carries the evidence for it, and the ones the evidence stops backing retire.

Rules that earn
their place

Every rule carries its evidence: how often reviews applied it, and whether later pull requests agreed with it. With the lifecycle on automatic, rules that keep being contradicted, or that nothing has needed for 120 days, move to Retired on their own with the reason recorded. Pin the ones that should never move.

How it works

Teach it from
the pull request

Comment @inline learn on any pull request, followed by the rule, and inline applies it to future reviews of that repository. @inline learn global stores it for every repository in the workspace. A rule can narrow to a path glob, a language or both, so it only rides along when a pull request changes a file it matches.

Drafted from what
your team does

When your team keeps dismissing the same kind of finding across several pull requests, inline drafts a rule to stop raising it. When the team keeps fixing one, it drafts a rule to keep raising it. Either lands in Suggested first, with the findings and pull requests behind it, for an admin to accept, edit or reject.

Some decisions stay
with a person

A rule that would silence bug or security findings never activates on its own. A rule a person retired or dismissed never comes back by itself, and a pinned rule never moves. Switch the automatic lifecycle off and every change becomes a person's decision. Each review lists the rules it carried, so you can see a rule at work.

Included

Active, Suggested, Retiredeach rule with its health and the team's verdicts
Scopeda workspace, a repository, a path glob or a language
Recorded per reviewevery review lists the rules it carried
Pinkeeps a rule on whatever the feedback says
Thresholds on the pagethe numbers behind every move are printed
Full historyevery move recorded with the numbers behind it

Put it on one repository

Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.