Troubleshooting: Pull Requests Are Not Showing in LinearB

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

What it means:
If the branch behind the PR contains only non-meaningful commits, LinearB excludes the PR from tracking. A non-meaningful commit does not represent original development 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 code author differs from the committer may be excluded. Common examples include:
   • Patches written by one developer and committed by another
   • Commits rewritten during rebases or cherry-picks
   • Squashed commits
   • Commits created by CI systems or bots on behalf of developers
2. The commit is a merge commit
   Merge commits are excluded because they consolidate work already counted in earlier commits.
3. Author is an excluded contributor
   Commits authored by contributors on the excluded list (for example, bots or service accounts) are ignored.
4. No substantial code or file changes
   Commits containing only formatting, whitespace, or other non-functional changes may be skipped.

Do the following:

• Ensure commits include meaningful code or file changes
• Avoid rebasing or squashing in ways that alter authorship unless required
• Verify contributors are not on the excluded list
• Review CI processes to ensure bots are not committing code that should be attributed to developers

What it means:
The PR may be ignored if its source or target branch matches an exclusion rule configured in your Git settings.

Do the following:

1. Review the Branch Exclusion Settings under Git settings in LinearB
2. Adjust the source or target branch rules as needed

See: Excluding Branches and Files from Git Metrics Dashboards

What it means:
Certain contributors—such as bots or system accounts— may be excluded from tracking at your organization’s request.

Do the following:

If you believe a contributor was excluded by mistake, contact your internal administrator or reach out to LinearB Support to review the exclusion list.

What it means:
Draft pull requests are ignored by LinearB until they are marked as Ready for Review.

Do the following:

Mark the PR as Ready for Review in your Git provider (GitHub, GitLab, Bitbucket, or Azure DevOps).

What it means:
Some LinearB metrics include only merged PRs. PRs that are still open or were closed without merging may not appear.

Do the following:

• Confirm the pull request was merged
• For metrics that track open PRs, review the selected filters and time ranges

What it means:
If your organization tracks only specific repositories or branches, the PR may fall outside that scope.

Do the following:

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

What it means:
LinearB starts tracking pull requests only after the Git integration is connected. PRs created before the integration are not imported retroactively.

This is expected behavior. Older PRs will not appear in LinearB.