Skip to main content
Add .macroscope/ignore.md at the repository root, with one glob pattern per line. Blank lines and lines beginning with # are ignored. Your file replaces the default patterns. Copy any defaults you want to keep. Tests remain excluded unless you set ignoreTests: false.
Use bare patterns, without Markdown bullets, backticks, quotes, leading /, or trailing comments. Maximum: 1,000 patterns.

Reviewing test code

Test detection uses paths and language naming conventions, such as _test.go or __tests__/. To review tests:
Omitted or true keeps test detection enabled. Explicit patterns still exclude matching files, so remove test patterns you copied from the defaults if you want those files reviewed. A test inside a file whose path does not look like a test is reviewed as ordinary code. Front matter must contain a recognized key. Unrecognized or malformed front matter produces a warning on the check; it is not silently applied as configuration.

Scope and precedence

Macroscope uses the first existing file, even if empty:
  1. .macroscope/ignore.md
  2. .macroscope/ignore
  3. .macroscope-ignore
On PRs, configuration comes from the latest PR commit. External forks use the default branch. CLI reviews use the latest committed version on the reviewed branch, so an uncommitted ignore-file edit has no effect. Ignore rules apply to correctness, CLI reviews, and Check Run Agents. They do not affect Status, commit summaries, or Slack queries. Ignored files are excluded from correctness review charges. Manual review requests do not override ignores. An explicit include in custom correctness instructions or a Check Run Agent can restore ignored files. The same configuration’s exclude still wins. Unreviewable binaries are always excluded.

Default ignore patterns

These are the overridable defaults for repositories without an ignore file. Binary exclusions also apply independently of this list.