Expand 'My work' to show PRs across all repositories, not just repos with sessions

Open
#4,068 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github
Domain
full-stack

Research direction

Start at the My work PR-list entry point and trace how repositories are currently limited to those with sessions. Compare that data source with the GitHub-wide access used by notifications or the GitHub PR list. Done means My work includes the user's authored and review-requested PRs across accessible repositories without requiring a session.

Written by the indexing model from the issue text.

Description

Summary

Expand "My work" to show pull requests from all repositories the user has access to.

Motivation

"My work" is close to being a great PR review dashboard, but it currently only surfaces PRs tied to repos where I've already started a session. For anyone working across many repositories, that means most of my open PRs never show up, and I have to go find them elsewhere.

If "My work" showed PRs across all of my repositories (based on GitHub permissions, same as notifications or the GitHub PR list), it would become a genuinely useful single place to track and review PRs, regardless of whether I've opened a Copilot session against that repo.

Proposed Solution

Source the PR list in "My work" from the user's GitHub-wide access (e.g. PRs authored by or requesting review from the user, across all repos they can see) instead of scoping it to repos with existing session history.

Alternatives Considered

A manual "add repos to My work" option, so users can opt specific repos in without a session, would be a smaller step in the same direction if full account-wide scoping isn't feasible.

Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/app

All issues in github/app

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.