Pull requests

The Pull requests tab sets two judgements Limn makes about every pull request: whether it is large, and how far its change can reach (its blast radius). Both settings apply to every workspace and take effect everywhere as soon as you save.

#Large pull requests

Limn flags a pull request as large when it changes at least a set number of lines of code. Only lines of code count. Documentation, configuration, lockfiles and generated or copied-in (vendored) files are left out, so a 4,000-line lockfile update is not a large pull request.

• Type a whole number greater than zero, then select Save.
• Clear the box and save to go back to the default of 1,500 lines.

#Blast radius

Blast radius is the Low, Medium or High chip shown beside each pull request. It reads what a change touches, not how big it is: a four-line database migration is High, and a 2,000-line documentation update is Low. A change that only edits comments or formatting is never lower than Medium. The chip is an estimate. See Blast radius for how to read it.

Sensitivity

Choose how readily a pull request counts as Low:

• Cautious: fewer pull requests count as Low. Good when a mistake is expensive to undo.
• Balanced: the default. On a typical repository about a third of open pull requests land in each level.
• Relaxed: more pull requests count as Low. Good for a fast-moving repository you can roll back easily.

Ignore these when judging reach

Some areas make a pull request High however small it is. Tick an area to ignore it when your repository is simply made of it. For example, a project whose product is a database schema would otherwise see almost every change marked High. The areas are:

• Database migrations
• Database schemas and models
• SQL files
• Published type definitions
• Service contracts (protobuf, GraphQL, Thrift)
• API descriptions (OpenAPI, Swagger)
• Infrastructure (Terraform, Helm, Kubernetes)
• Auth and security code