mirror of
https://github.com/jesseduffield/lazygit.git
synced 2026-09-10 07:36:27 -04:00
096a710761
When the user picks a base remote in the "select remote repository" prompt, we called setGithubPullRequests directly, bypassing the refresh machinery — which meant hand-rolling the refresh env that call needs (with a comment explaining why), and fetching against the branches captured when the prompt was created. Issue a PULL_REQUESTS-scoped refresh instead: it re-reads branches and remotes (both fast even in large repos), fetches against those fresh values, and gets the refresh machinery's guarantees without any special-casing. The config write is re-read by the refresh from git config, so it is guaranteed to be picked up. The waiting status now covers the config write and the branches/remotes reload, while the GitHub request itself continues as a background task — which is how every other pull-request fetch behaves. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| app | ||
| cheatsheet | ||
| commands | ||
| common | ||
| config | ||
| constants | ||
| env | ||
| fakes | ||
| gocui | ||
| gui | ||
| i18n | ||
| integration | ||
| jsonschema | ||
| logs | ||
| snake | ||
| tasks | ||
| theme | ||
| updates | ||
| utils | ||