Skip to main content
Open a repository in Scopy to view its pull requests and review activity.

​
Pull request list

The repository detail page has a pull request list. Selecting a pull request opens the detail panel for that PR. The list and detail panel help you inspect:
  • Pull request metadata.
  • Current review state.
  • Timeline events.
  • Published findings and review output.

​
GitHub comments

When Scopy confirms findings, it publishes feedback back to GitHub. Findings are intended to be line-specific when possible so authors can act on them directly in the pull request. Scopy also maintains a summary comment for the PR review run.

​
Manual review triggers

If a pull request needs another pass, mention the GitHub App in a pull request comment. Scopy treats that as an on-demand trigger and queues a fresh review for enabled repositories.

​
Skipped reviews

Scopy may skip a review instead of running analysis. When that happens, the run is marked skipped and Scopy posts a summary comment on GitHub with the reason. Common skip reasons:
  • No matching path filters - After applying the repository’s include and exclude path patterns, no changed files remain to review. Workspace defaults exclude **/*.json.
  • Changed line limit exceeded - The pull request changes more reviewable lines than the configured maximum. Reviewable line count is the sum of additions and deletions on files that pass path filters.
  • Not enough credits - The workspace has no remaining review credits. See Billing.
The default maximum changed lines is 15,000. You can adjust this limit and path patterns in repository review settings. The limit can be set anywhere from 1 to 100,000 changed lines. When a review is skipped, Scopy records the skip reason on the review run instead of publishing findings.