Repository ignores
An ignore map in bolvrk.json silences a rule for a whole repository with a reason that travels with the code; the CLI and the Action send it along, and hosted checks honor it on Startup and above. Every report says how many findings it hid.
Some rules are house style — timestamp without time zone, char(n), serial — and a repository that has decided against them should not see the note on every pull request. The ignore map in bolvrk.json silences a rule for the whole repository. The reason is required, and it lives next to the code so the next reader knows the decision was made, not missed.
The CLI and the Action send the map with hosted checks, where it is honoured on Startup and above, before the team policy. --ignore=BV040 does the same for one run. The output always says how many findings were hidden — an ignore never makes a report look cleaner than it is.
{
"ignore": {
"BV040": "timestamp without time zone is our house style",
"BV043": "serial columns are generated by our ORM"
}
}One finding, not one rule
To accept a single occurrence, use the inline directive on the statement instead: -- bolvrk-ignore BV003: index built in the maintenance window. It is part of the engine and applies everywhere, and every attempt — honoured or refused for a missing reason — is recorded in the report.
The CLI is open source and needs no account: npx bolvrk check migration.sql