Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/codacy-cloud-cli/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,9 @@ codacy findings gh my-org my-repo --severities Critical,High
# Filter by scan type
codacy findings gh my-org --scan-types SAST,Secrets
codacy findings gh my-org --scan-types SCA,IaC --severities High

# Container scanning findings for one image
codacy findings gh my-org --scan-types ContainerSCA --image myorg/app:1.4.2
```

Findings are tracked with statuses like `Overdue`, `OnTrack`, and `DueSoon`. Use `--statuses` to filter accordingly:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ A review can contain:
- **Test suggestions** for the scenarios the changes should test.
- **Inline comments** on the lines that need attention, most with a suggested fix. React 👍 if a comment is right, or reply with what's wrong. The AI Reviewer [learns from these reactions and replies](../../codacy-ai/codacy-ai.md#learning-from-reviews).
- **General comments** for requirements it finds the changes don't implement.
- **Tips** under "Make this review better" with what you can add to get a better review.
- **A tip** with one thing you can add to get a better review, such as review instructions, a pull request description, or a Jira or Linear ticket key.

When you run the reviewer again on the same pull request, it reads the comments from its earlier reviews so it doesn't raise the same point twice, unless new commits changed that code substantially.

Expand Down
Loading