Troubleshooting: Why Are My Pull Requests Not Showing?

If you’re not receiving notifications for your pull requests (PRs), or you can’t find them in your LinearB Metrics or Activity views, the PRs may be excluded from tracking. This article outlines the most common reasons why a PR might not appear and how to resolve each issue.

Symptoms

• No notifications are generated on pull requests
• PRs are missing from the Metrics tab and/or the Activity feed

Common Causes and Fixes

PR has no meaningful commits

What it means: If the branch behind the PR contains only commits that are considered non-meaningful, LinearB will exclude the PR from tracking. A “non-meaningful” commit is one that doesn’t reflect original development work or real code changes.

When does this happen? A commit may be excluded if it meets any of the following criteria:

1. Author ≠ Committer
   Commits where the person who wrote the code (Author) is different from the person who committed it (Committer) may be excluded.
   Common examples:
   • A patch written by one developer and committed by another.
   • Commits rewritten during a rebase or cherry-pick.
   • Squashed commits.
   • Commits made by CI systems or bots on behalf of developers.
2. The commit is a merge commit
   Merge commits are excluded because they consolidate changes that have already been counted from previous commits.
3. Author Is an excluded contributor
   If the commit author is on your organization’s excluded contributors list (e.g., bots or service accounts), their commits will be ignored.
4. No substantial code or file changes
   Commits that include only formatting, whitespace, or other non-functional updates may be skipped.

Do the following: 

• Ensure your commits include meaningful code or file changes.
• Avoid rebasing or squashing in ways that change authorship unless necessary.
• Confirm that the contributors involved are not on the excluded list.
• Review your CI processes to ensure bots aren’t committing code that should be attributed to developers.

PR comes from an excluded branch

What it means: Your PR may be ignored if its source or target branch matches a branch exclusion rule configured in your workspace settings.

Do the following:

1. In LinearB, check the Branch Exclusion Settings under Git settings.
2. Adjust the source or target branch rules as needed.

See: Excluding Branches and Files from Git Metrics Dashboards

Author Is an excluded contributor

What it means: Some contributors—like bots or system accounts—may be manually excluded by LinearB support at the request of your organization.

Do the following: If you think a contributor was excluded by mistake, contact your internal admin or LinearB support to review the exclusion list.

PR is in draft mode

What it means: Draft PRs are ignored by LinearB until they’re marked as Ready for Review.

Do the following: Mark the PR as Ready for Review in your Git provider (e.g., GitHub, GitLab, Bitbucket, Azure DevOps).

PR is not merged

What it means: Some LinearB metrics only include merged PRs, so if a PR is still open or was closed without merging, it may not show up.

Do the following:

• Confirm the PR was merged.
• For metrics that track open PRs, check the relevant filters and time ranges

PR is filtered by repo/branch rules

What it means: If your organization has set up project filters—like only tracking certain repositories or branches—the PR may fall outside those filters.

Do the following:

• Review your team’s Project Tracker or Git settings.
• Ensure the PR’s repo and branch are included in your tracking scope

PR was created before Git integration

What it means: LinearB begins tracking PRs only after your Git integration is connected. It does not fetch PRs created beforehand.

This is expected behavior. Older PRs will not appear retroactively.

If none of these solutions resolve your issue, please reach out to LinearB Support with details about the missing PR.