[Bugs] Pull Request doesn't load when it's targeting an upstream repo.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Mood:** 😊
**Category:** Bugs
Pull Request doesn't load when it's targeting an upstream repo. And for some reason, the PR view's tab says Issue instead of Pull Request. When the pull request targets the same repository (fork in my case), the PR view can load.
Clicking the link to the created PR in the response opens the PR in the integrated PR view. Across all my attempts, the view keeps loading and doesn't show anything no matter how long I wait.
Additional context:
Forking an upstream repo, develop in the fork and submit a PR to the upstream from the fork is a typical GitHub workflow.
The built-in PR tool in the app only knows how to create a PR in the same repo. In this case, it is the forked repo and that's not what I want.
I was able to work around this problem by explicitly emphasize in my prompt telling the agent to use gh cli and giving the exact upstream org/repo - branch target. It mitigates the problem most of the time but occasionally it still hallucinates by creating the PR in the forked repo claiming it has created it in the upstream.
The screenshots contains both a working PR view 24 which was incorrectly created in the forked repo, and a buggy view 2725 in the upstream repo.
---
| Field | Value |
| --- | --- |
| App version | 1.0.11 |
| OS | macOS 14.8.7 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 5 |
Guía de contribución
Línea de trabajo
Reproduce el problema en la vista de PR integrada usando un fork que apunte a un repositorio upstream y compáralo con el caso funcional del mismo repositorio descrito en el informe. Comprueba por qué la vista upstream sigue cargando y está etiquetada como Issue; se considera terminado cuando el PR upstream carga y la pestaña lo identifica como Pull Request.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github
- Área
- desktop
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100