c719d920c3
When running `gh repo fork` in the context of an existing repo, the CLI offers to create a remote for the fork: ``` ? Would you like to add a remote for the fork? Yes ``` If you accept, it prints a log stating that the `origin` remote has been created: ``` ✓ Added remote origin ``` Where there is an existing `origin` remote, this is renamed to `upstream`, but this is done silently without any notification to the user. ```bash $ git remote -v origin https://github.com/timrogers/badger.github.io.git (fetch) origin https://github.com/timrogers/badger.github.io.git (push) upstream https://github.com/badger/badger.github.io.git (fetch) upstream https://github.com/badger/badger.github.io.git (push) ``` It seems kinda fine to rename the remote without explicitly confirming since this is not a truly destructive action, but it should make it clear what it is doing. This updates the logging to explicitly log about the renaming of the existing remote: ``` ✓ Renamed remote origin to upstream ``` Fixes #9982. |
||
|---|---|---|
| .. | ||
| cmd | ||
| cmdutil | ||
| extensions | ||
| findsh | ||
| githubtemplate | ||
| httpmock | ||
| iostreams | ||
| jsoncolor | ||
| jsonfieldstest | ||
| markdown | ||
| option | ||
| search | ||
| set | ||
| ssh | ||
| surveyext | ||