Skip to content
MergeRay/ docs

Search documentation

Local documentation search Tab to navigate · Esc to close

Configuration

Keep review policy explicit, declarative and tied to trusted source.

On this page Where policy comes fromPolicy exampleExclusions and rule overrides

Where policy comes from

Use declarative JSON. The Action reads mergeray.policy.json from the exact trusted Base commit, not from Head. The CLI accepts an explicit trusted JSON file with --config. Neither entry point executes JavaScript or TypeScript configuration.

The example below is a policy shape, not an installation command. The hosted service independently enforces its authorized policy.

Policy example

mergeray.policy.json
{
  "scope": {
    "kind": "repository",
    "selectionProfile": "authored-source-1"
  },
  "transferExclusions": [],
  "rules": [],
  "gate": {
    "changes": "introduced-or-worsened",
    "minimumSeverity": "warning"
  }
}
JSONRead-only

Exclusions and rule overrides

  • Transfer exclusions use literal repository-relative file or directory paths, not globs. Required excluded source makes coverage incomplete.
  • Rule overrides set ruleId, enabled and severity. Unknown keys, invalid paths and executable values are rejected.
  • Existing legacy ignore and policy compatibility remains in the clients. Invalid canonical policy is not silently replaced with legacy policy.
Read the public configuration reference