> ## Documentation Index
> Fetch the complete documentation index at: https://roe.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Suppressing findings

> Mark false positives with inline comments or ignore globs.

Two mechanisms let you mark a finding as a false positive: inline comments
for individual lines, and [config-file `ignore` globs](/configuration) for
whole files and directories.

## Inline comments

Inline comments work eslint-style and are checked after the first `//` on a
line, so `///` doc-comments match too:

```csharp theme={null}
// roe-ignore-next-line unused-type
internal class LegacyHelper { }

public void DoWork()
{
    var unused = 1; // roe-ignore-line unused-member
}
```

`roe-ignore-next-line` suppresses a finding on the line below the comment;
`roe-ignore-line` suppresses one on the same line.

Both take an optional comma-separated rule list — omitting it suppresses any
finding kind on that line.

For [`roe dead-code`](/commands/dead-code):

| Rule            | Suppresses                |
| --------------- | ------------------------- |
| `unused-type`   | An unused type finding.   |
| `unused-member` | An unused member finding. |
| `unused-file`   | A dead file finding.      |

For [`roe health`](/commands/health):

| Rule                        | Suppresses                            |
| --------------------------- | ------------------------------------- |
| `high-complexity`           | A cyclomatic complexity finding.      |
| `high-cognitive-complexity` | A cognitive complexity finding.       |
| `long-method`               | A long method body finding.           |
| `too-many-parameters`       | An over-parameterized method finding. |
| `large-file`                | A large file finding.                 |
| `large-type`                | A large type finding.                 |

These are the same names used in the `kind` field of
[JSON output](/reference/json-output).

Because the list is comma-separated, one marker can silence exactly the
checks you've accepted while leaving the rest reported:

```csharp theme={null}
// roe-ignore-next-line high-complexity,long-method
public void ParseEverything(string input)
```

<Note>
  A dead file's finding and a large file's finding are both pinned at line 1,
  so an `unused-file` or `large-file` marker — or a bare marker with no rule
  list — suppresses them from anywhere in the file.
</Note>

## Ignore globs

To drop every finding in matching files — for `dead-code`, `dupes`, and
`health` alike — use the `ignore` list in a config file:

```json roe.json theme={null}
{
  "ignore": ["Migrations/**", "Generated/", "**/*.designer.cs"]
}
```

To keep a suppression as narrow as the exception it accepts, scope it to one
command instead: each command's section takes an `ignore` list of its own,
unioned with the top-level one and applied only to that command. Accepting
an intentional duplicate this way doesn't cost the file its dead-code and
health coverage:

```json roe.json theme={null}
{
  "dupes": {
    "ignore": ["**/InsurerUnionQuery.cs"]
  }
}
```

See [Configuration](/configuration) for glob semantics and config discovery.

<Note>
  Duplicate groups and circular dependencies span multiple files, so neither
  maps onto a single-line comment and neither has an inline suppression.
  Ignore globs — top-level, `dupes.ignore`, or `health.ignore` — are the only
  way to silence them.
</Note>