[Bugs] Pull Request doesn't load when it's targeting an upstream repo.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 2.1k
- Fork
- 153
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**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 |
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Reproduce the issue in the integrated PR view using a fork targeting an upstream repository, then compare it with the working same-repository case described in the report. Check why the upstream view remains loading and is labeled Issue; done means the upstream PR loads and the tab identifies it as Pull Request.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- github
- Ambito
- desktop
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100