Add a direct link to the pull request from the PR pane
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Área
- developer-experience, tooling
Línea de trabajo
Find the PR pane component in the GitHub Copilot app's codebase, likely in a frontend directory. Look for where PR data is displayed and add a link that constructs the canonical GitHub.com URL from the owner, repo, and PR number. Test the change by running the app locally and verifying the link opens the correct browser page.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature summary
Add an obvious direct link from the GitHub Copilot app's PR pane to the corresponding pull request on GitHub.com.
What problem are you trying to solve?
The PR functionality inside the GitHub app is currently useful but limited compared with the full GitHub.com pull request page. When a user is reviewing or working from the app's PR pane and needs functionality that is only available on GitHub.com, there should be a quick way to jump to the source PR.
Right now, if the pane does not expose the PR URL, the user has to manually search for the PR or navigate through the repository/issues UI to find it. That breaks flow and makes the app feel like a dead end when the in-app PR experience is missing a needed action or detail.
Proposed solution
Show a clear “Open pull request on GitHub” link or button in the PR pane. This could live near the PR title, in an overflow menu, or anywhere consistently available while viewing a PR.
The action should open the canonical PR URL in the browser, for example:
https://github.com/<owner>/<repo>/pull/<number>
Workflow impact
This would make the PR pane safer and easier to use as a starting point, even while the in-app PR functionality is still limited. Users could stay in the app for supported flows and quickly escape to the full GitHub.com PR page when they need advanced review, checks, files, comments, merge controls, links, or other details.
Installation context
GitHub Copilot desktop app; PR pane / pull request workflow.
Additional context
This is especially useful while the app's PR functionality is still maturing: even if the app cannot support every PR action immediately, a direct canonical PR link gives users a reliable fallback.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.2k
- Forks
- 174
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la 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 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
triage
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 70/100
Todos los issues de github/app
Issues similares
-
Claiming namespace `apoint`Abiertonamespace operations
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
EclipseFdn/open-vsx.org#13573 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
HenriquesLab/rxiv-maker#335 ·
-
chore.Load accepts duplicate BUTLER_CHORES names, double-counting the butler's daily budgetsAbiertoagent-butler-finding bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
jordansmall/spindrift#4143 ·
Los mantenedores suelen responder en 1 día
-
`TypeError: '<=' not supported between instances of 'NoneType' and 'int'` when checking metaclassesAbiertoNeeds triage :inbox_tray:
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
pylint-dev/pylint#11511 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
grikomsn/openai-oauth-copilot-chat#61 ·
Los mantenedores suelen responder en 1 día