feat(issues): add --state ignored to list ignored issues OD-318

[claudiacodacy]

What

Adds codacy issues --state <active|ignored> (-S) — a read-only way to list issues that were marked as ignored on Codacy.

--state defaults to active, so codacy issues … behaves exactly as before. Pass --state ignored to see the ignored ones.

$ codacy issues --state ignored --limit 5

Ignored Issues — Found 22 issues

Critical | Complexity  2b7d782d922ca6c25479637e4f06d49d
Method (anonymous) has 108 lines of code (limit is 100)

src/commands/tools.ts:74
.action(async function (

Ignored as FalsePositive by alerizzo · 2026-05-27
────────────────────────────────────────

How

• Backed by the dedicated searchRepositoryIgnoredIssues endpoint (.../ignoredIssues/search), which accepts the same filter body as the normal search — so --branch, --patterns, --tools, --severities, --categories, --languages, --tags, --authors, --limit, and --false-positives all pass through unchanged (reuses buildFilterBody + the paginate-to---limit loop).
• New printIgnoredIssueCard in utils/formatting.ts — a variant of printIssueCard, since IgnoredIssue has no numeric resultDataId (shows the string issueId) and carries ignore metadata (Ignored as <reason> by <name> · <date> + optional Comment:).
• Guards: errors when combined with --overview (no ignored-issues overview endpoint) or --ignore (already ignored). --false-positives is intentionally allowed.
• --output json emits { ignoredIssues: [...] } projected via pickDeep to the shown fields.

Design decisions (consistency + UX)

• Mode-flag on issues, not a new command — issues already models sub-modes (--overview, --ignore, --false-positives); a new command would duplicate all the filter-parsing plumbing.
• --state active|ignored selector rather than a --ignored boolean — a boolean would sit one case-flip away from the existing -I/--ignore (opposite effect), an easy footgun. -S because -s is --severities (the repo's uppercase-when-taken rule). The active default keeps full backward compatibility.
• state over status — "status" is already used in the codebase for analysis status.
• View-only scope — unignoring stays with issue --unignore; there is no bulk-unignore endpoint (a possible fast-follow, since IgnoredIssue carries the string issueId).

Testing

• 11 new tests (476 total, all passing): rendering + metadata/comment, filter pass-through, --false-positives allowed, pagination + warning, JSON projection, invalid --state, both guards, and a regression that bare issues still hits the active endpoint.
• check-types clean.
• Verified live against codacy/codacy-cloud-cli: table, JSON, and guard paths all behave as designed.

Changeset: minor (new capability on an existing command, non-breaking — matches how comparable additions were versioned).

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics -3 duplication

Metric	Results
Duplication	-3

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[gemini-code-assist]

Code Review

This pull request introduces a new --state <active|ignored> (-S) option to the codacy issues command, allowing users to list issues that have been marked as ignored on Codacy. It integrates the dedicated searchRepositoryIgnoredIssues API endpoint, supports existing filters, and implements a new card renderer (printIgnoredIssueCard) to display ignore metadata such as the reason, author, timestamp, and optional comments. Comprehensive tests and documentation have also been added. There are no review comments, and no feedback is provided.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[codacy-production]

Pull Request Overview

This PR adds support for viewing ignored issues via the --state flag. While functionally complete and correctly integrated with the relevant API endpoints, the automated analysis indicates the PR is not up to standards. The primary concerns are code duplication (clones) between active and ignored issue card rendering and high complexity in the new test blocks. Addressing the duplication in src/utils/formatting.ts and refactoring mock data in src/commands/issues.test.ts are recommended to meet quality requirements.

About this PR

• The PR is currently failing quality standards. The new logic for ignored issues duplicates significant portions of the existing active issues formatting. Refactoring the shared card components is necessary to reduce the technical debt introduced by this feature.

Test suggestions

• Verify listing ignored issues renders metadata line and comments correctly in table output
• Verify filters (e.g. severities, categories) are correctly passed to the ignored issues API endpoint
• Verify pagination logic works and shows a warning when more issues exist beyond the limit
• Verify JSON output contains only the projected fields defined in the design
• Verify error is thrown when combining --state ignored with --overview
• Verify error is thrown when combining --state ignored with --ignore
• Verify default command (no --state) still hits the active issues endpoint

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}