When someone edits files inside third-party folders, like vendor, generated, or some internal lib, it’s common for Kody to start generating suggestions on those parts. The problem is that, in most cases, the team doesn’t even plan to review those points, since they’re areas of the code that usually aren’t changed manually.
If the goal is to reduce this kind of noise in reviews, there are two ways to adjust Kody’s behavior:
Option 1: Completely ignore files from these folders
The most straightforward way is to configure Kody to simply ignore any files inside these folders. That way, it won’t review them or generate comments.
Just go to Settings → General Settings → Ignored Files and add the paths the team wants to ignore, one per line.
Example:
vendor/**
generated/**
Option 2: Create a Custom Rule to flag changes in these folders
If the team still wants to be alerted whenever someone touches these folders, but without getting line-by-line suggestions in each file, an alternative is to create a Custom Rule focused only on flagging the PR.
Important:
Kody doesn’t have a specific type of “general warning.” Every rule will always generate a suggestion inside the PR if its severity is equal to or above the minimum severity level configured in the Review Settings.
If the team wants the suggestion to only appear in more permissive scenarios (e.g., during a manual review or with a lower global filter), you can configure the rule with Low Severity.
Example configuration:
- Rule name: “Avoid changes in third-party or generated folders (vendor, generated, etc)”
- Path:
/vendor/**,/generated/**(or any other paths the team wants to monitor) - Severity: Low
- Instructions:
“Avoid making changes to generated or third-party folders unless absolutely necessary.”
With these adjustments, the team can significantly reduce the noise in PR reviews that touch third-party or auto-generated folders.
