​
Why is my analysis timing out?

DeepSource currently has a 25-minute time limit for completing analysis. If analysis doesn’t finish within this period, you’ll see an “Analysis timed out” message. Common causes:
  • First-time analysis of a repository (when all files are analyzed)
  • Large repositories with many files
  • Complex code that requires deeper analysis
Solutions:
  1. Configure exclude_patterns in your .deepsource.toml file to skip unnecessary files like:
    • Test fixtures
    • Migration files
    • Example code
    • Generated code
    • Third-party libraries

​
Why do I see test coverage issues for lines that have not changed in my PR?

This typically occurs when your PR branch is not up-to-date with the default branch. Solution: Rebase your PR branch with the default branch to synchronize the code and resolve this discrepancy.

​
DeepSource generated the wrong Autofix. How do I report it?

If you notice an incorrect Autofix suggestion:
  1. Take a screenshot or copy the relevant code snippet
  2. Reach out to Support:
    • The screenshot/code snippet
    • A brief explanation of why the Autofix is incorrect
    • Name of the repository

​
Analysis fails, with the message “Error cloning git repository”. What should I do?

This error can occur for several reasons:
  1. Submodule issues
    • If your repository uses Git submodules, ensure DeepSource has access to them
    • Configure submodule access in your repository settings
  2. Default branch mismatch
    • If your default branch has changed (e.g., from “master” to “main”), update this in DeepSource
    • Navigate to Settings > General to change the default branch name
    • Learn more about branch settings
  3. VCS provider downtime
    • Rarely, this can be due to GitHub/GitLab/Bitbucket/AzureDevOps service issues and downtime
    • Check status page of respective services and wait a short while and retry the analysis

​
Why can’t I find the option to add team members?

This happens when you’re using an Individual account rather than a Team/Organization account. Account types:
  • Individual accounts are connected to personal GitHub, GitLab, Bitbucket or AzureDevOps accounts and don’t support adding team members
  • Team/Organization accounts are linked to GitHub organizations, GitLab groups, Bitbucket workspaces or AzureDevOps organizations
Solution: To add team members, you need to use a Team/Organization account. Learn more about account management and adding team members.

​
DeepSource shows issues in all files of the repository even when granular mode is selected

This occurs when a PR is opened against a non-default branch instead of the default branch. Solution: Open your PR against the default branch to enable proper granular analysis.
We don’t currently support diff analysis on non-default branches, but this feature is on our roadmap.

​
Analysis results are different on the same change in PR and in the default branch

When a PR includes changes to the .deepsource.toml configuration file, analysis results may differ between the PR and after merging to the default branch. Why this happens: Configuration changes (like new exclude patterns or analyzer options) can affect how existing issues are reported. When merging to the default branch, DeepSource performs a full analysis with the updated configuration to ensure consistency. Expected behavior:
  • PRs receive granular analysis based on their specific changes
  • Default branch receives full analysis after merging configuration changes to ensure all issues are properly updated