Appearance
Using the dashboard
The dashboard is where you follow reviews, open their findings, and manage the repositories you can access.

The organization switcher
Use the switcher to choose one installation or view all installations you can access. It scopes the dashboard, repositories, reviews, settings, and members pages. Your choice is remembered between visits.

Choose Manage installations to change the GitHub App's repository access.
Technical and Decision view
| View | Best for | Focus |
|---|---|---|
| Technical view | Developers working through a review | Files, line-level findings, diffs and individual evidence |
| Decision view | People deciding whether a change is ready | Plain-language impact, merge guidance and project status |
The choice is personal. It changes neither the GitHub review nor what teammates see.

Dashboard home
Technical view summarises completed reviews, review activity, repository health, and work still in progress. Decision view focuses on project status across repositories.
Use Sync From GitHub when repository access has changed or a new installation is missing.
Stale repository list
Try Sync From GitHub before reinstalling the App. It re-reads every installation and repository your GitHub account can currently access.
Merge confidence
Completed reviews can be rated High, Medium, or Low. The dashboard groups completed ratings to show the share of reviews with each result. A review without a rating is shown as Unrated and is not included in that percentage.
Confidence is review guidance, not a guarantee that a pull request is correct or safe to merge. See Reading a review.
Failed reviews this month
When reviews have failed, a banner above the review activity reads, for example, 3 pull requests failed this month and can be re-run. It counts pull requests whose latest review failed during the current calendar month, in UTC; earlier failures are not counted.
- View all failures opens the Reviews page filtered to failed reviews, from any month.
- Re-run 3 failed this month retries those pull requests in one go. It is shown to admins of the selected organization, not under All organizations. Each pull request is retried only when your plan and quota allow a review.
Repositories and reviews
The Repositories page shows repositories covered by your installations and whether reviews are enabled. Open a repository to see its project status, settings, and reviews.
The Reviews page lists pull requests by their latest review. Filter by repository, status, or author. A row updates while a review is running and opens the review detail.
Where spec review is on, a row also shows the result of a finished spec check next to its comment count. Hover over the label for a short explanation.
| Label | Meaning |
|---|---|
| 2 conflicts (red) | The code contradicts a specification, with the number of conflicts found. Open the review to see where. |
| 2/2 specs checked (blue) | Every relevant specification was compared and no conflicts were found. |
| 1/2 specs checked (amber) | No conflicts were found, but not every relevant specification was checked, so conflicts may be missing. |
A row shows no spec label while the spec check is still running, when no specification applied to the change, or when the check did not finish. Open the review to see its spec result. A blue label means only that nothing contradicted the specifications compared, not that the change follows all of them.
Reading a review in the dashboard
The detail page shows the review's status, files and findings, and whether each finding was posted to GitHub; see Reading a review. You can retry the latest eligible failed review from here, or push a new commit.
With spec review on, its result appears with the code review. No relevant specification applies is not an error. When conflicts were found, the spec review header shows how many. Otherwise, in Technical view it shows how many relevant specification files were checked, for example 2/2 files checked: blue when every one was checked, amber when some were not, so conflicts may be missing. Decision view shows No conflicts found instead. Either way, this means only that nothing contradicted the specifications compared, not that the change follows all of them.
Re-running the spec review
After changing a specification, you can re-run the spec check for the latest completed review of an open pull request. It rechecks the specification only, not the code review. Each review can be re-run twice; push a new commit after that.

If the pull request has no code changes the spec check can compare, for example because every changed file is excluded, nothing is re-run and the re-run is not counted: No eligible code diff to compare. The previous spec review result is unchanged.
Settings and members
Admins can change installation and repository settings. Members can view settings, reviews, and repositories. Membership and repository access continue to come from GitHub. See Organization settings.
Support
Use Report a problem on a review or repository to start a ticket with that context attached. See Help and support.