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

# Why did the comments on a PR or MR not appear inline?

> When Semgrep comments on PR or MR findings, the comments are usually posted on the line of code where the finding is identified (inline). However, there are two common reasons why comments may not appear inline.

## Avoiding excessive inline comments

For rules with several findings in the same PR or MR, inline comments for every individual finding occupy a significant amount of space without providing much additional information. Therefore, if the same finding occurs more than five times in a PR or MR, the related comment is posted as a summary (overall) comment. Findings grouped together into a summary comment can only be triaged in Semgrep AppSec Platform.

## Available lines in the displayed diff

### GitHub PRs

GitHub only allows PR comments to be posted on lines of code that are shown in the default file-diff (Files changed) view on GitHub. If a finding appears outside those lines, Semgrep attempts to post the comment as close to the finding as feasible. If that fails, it posts the comment as a summary comment, visible in the Conversation view.

### GitLab MRs

GitLab allows comments to be posted on lines of code outside the default file-diff view, but the comments don't appear in the file-diff (Changes) view. However, they do appear as diff-related comments on the Overview.

## Additional references

<CardGroup cols={2}>
  <Card title="Enabling GitHub pull request comments" horizontal href="/semgrep-appsec-platform/github-pr-comments" icon="file" />

  <Card title="Enabling GitLab merge request comments" horizontal href="/semgrep-appsec-platform/gitlab-mr-comments" icon="file" />

  <Card title="Enabling Bitbucket pull request comments" horizontal href="/category/bitbucket-pr-comments" icon="file" />
</CardGroup>