Use GitHub's new pulls dashboard to stop losing review work

GitHub has made its refreshed pull requests dashboard generally available at github.com/pulls. Confidence level: confirmed. The change gives developers and managers one place to track review requests, pull requests that need fixes, and branches ready to merge, instead of rebuilding the same searches across bookmarks and tabs.

What changed

GitHub announced general availability for the new pull requests dashboard on July 9, 2026. The dashboard was previously in public preview. It now acts as a dedicated review inbox with sections for review requests, PRs that need attention, and pull requests that are ready to merge or already in the merge queue.

The dashboard also adds saved views, smart default filters, auto-complete, keyboard navigation, and more expressive search. GitHub says users can now reorder or hide inbox sections, filter by repository or recent activity, and build custom views from frequently used search queries.

Why this is early

This is early in adoption, not early in confirmation. The GitHub Changelog marks the dashboard as generally available, and Microsoft's unified developer changelog lists the same GitHub update. The open question is how teams should reorganize review habits around the new inbox rather than whether the feature exists.

The timing matters because GitHub is adding more agent-created and Copilot-assisted pull request flows. A centralized dashboard becomes more useful when humans need to triage reviews, bot-created PRs, CI failures, and merge queues across several repositories.

Key takeaways

• github.com/pulls is now the main dashboard for pull requests needing your attention.
• Inbox sections can surface review requests, failing PRs, comments, branch-update states, and merge-ready work.
• Saved views let teams reuse common PR searches without relying on browser bookmarks.
• Advanced search now supports nested queries, AND/OR logic, and richer review filters.
• GitHub says author:@me now includes pull requests created by GitHub Copilot on your behalf.

Availability and access

The dashboard is live at github.com/pulls. GitHub describes the release as generally available, so it is no longer only a public-preview workflow. Teams should still check organization settings, enterprise policies, and whether their preferred filters behave the same way across personal repositories, organizations, and enterprise-managed projects.

The most useful new filters are team-review-requested-user, which finds PRs where you are included in a team review request, and review-involves, which finds PRs you were asked to review even if the current approval state changed.

Practical LinkLoot angle

This is a cleanup opportunity for review workflows. Replace scattered bookmarks such as is:open is:pr review-requested:@me with saved dashboard views for review queue, blocked CI, authored PRs, merge queue, team review requests, and agent-created PRs.

Teams using coding agents should create a dedicated saved view for Copilot-created or agent-assisted pull requests. That makes it easier to separate machine-generated work from human-authored changes without slowing down review. For broader agent workflow planning, LinkLoot's AI agent tools guide is a useful companion.

What to verify before you act

• Open github.com/pulls and confirm which inbox sections appear for your account.
• Test saved views against your most common PR queries before replacing bookmarks.
• Check whether team-review-requested-user:@me matches your team's review assignment process.
• Confirm whether author:@me includes Copilot-created pull requests in your repositories.
• Decide who owns triage for merge-ready, failing, and stale PR sections so the dashboard does not become another unread inbox.

Source check

Confirmed by: GitHub's July 9, 2026 changelog post and the GitHub Changelog index.

Independent context: Microsoft's Developer Changelog lists the same GitHub update in its unified developer feed. LinkLoot is treating this as a developer workflow update, not a security emergency or AI model release.