Last updated: November 17, 2025

Context

Sometimes the CodeRabbit bot will post a Caution in a comment as below.

Some comments are outside the diff and can’t be posted inline due to platform limitations.

This appears when CodeRabbit detects issues in parts of the file outside the modified lines of your pull request. While CodeRabbit reviews the entire file, platforms like GitHub, GitLab, Bitbucket, and Azure DevOps only allow inline comments on the specific lines changed in the diff.

Answer

When CodeRabbit reviews a pull request, it normally posts inline comments directly on the lines that were changed. However, if CodeRabbit finds an issue outside the diff — in unchanged or contextual lines — your Git platform will block inline comments on those lines. This is a limitation of GitHub, GitLab, Bitbucket, and Azure DevOps.

In these cases, CodeRabbit moves those comments into a summary section and includes the file name and line number for easy reference.

Example:

Your PR adds a new OAuth authentication method:

// Line 5 (unchanged)function validatePassword(password: string) {
    return password.length >= 6;  // Weak validation!
}

// Line 10 (unchanged)function hashPassword(password: string) {
    return crypto.createHash('md5').update(password).digest('hex');  // MD5 is insecure!
}

// Line 15–17 (YOUR CHANGES)function authenticateWithOAuth(token: string) {
    const user = await verifyOAuthToken(token);
    return { userId: user.id, email: user.email };
}

The diff only includes lines 15–17, but CodeRabbit also detects issues on lines 5 and 10:

• Line 5: Password validation is too weak

• Line 10: MD5 hashing is insecure

Because these lines are outside the diff, the platform won’t allow inline comments.
CodeRabbit therefore posts:

Some comments are outside the diff and can’t be posted inline due to platform limitations.

To review them, simply open the file and navigate to the referenced lines in your IDE or code viewer.

Why does this happen?

Most Git platforms only allow inline comments on:

• Lines added (+) or removed (-)

• A small number of context lines around the change

Anything outside this window cannot receive an inline comment through the platform’s API.

What to do

• Review the summary comments — they may include important security or quality issues.

• Navigate to the referenced lines using the file path and line number.

• Create follow-up PRs if the issues are valid but not within the scope of your current changes.