Expand 'My work' to show PRs across all repositories, not just repos with sessions
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github
- Área
- full-stack
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 157
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/app
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de github/app
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
pastelsky/bundlephobia#1122 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
speaches-ai/speaches#678 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jellyfin/jellyfin-web#8540 ·