its really common that origin/master is the original repo, and myusername/whatever is "my fork", and contains "my branches", and that "origin" is almost-certainly the WRONG repo to interact with, and the only way to "switch", is to Project Menu->Project Settings->scroll to very bottom -> Remove Project an to "start over" completely and go back to the new-project wizard. GitKraken allows this trivially by right-clicking on a 'remote' and choosing Edit, or Adding a new Remote to the list of remotes, can't seem to see any way to do either of those in gitbutler. it feels unusable without these basic capabilities to me.
How to reproduce
use the default and recommended settings on a repo that has "upstream" ( non-writable remote ) configured as origin/master and use recommeneded defaults during repo-chooser / initial configuration page.
Expected behavior
make the implications of choosing the wrong/default remote smaller and easier to fix, and dont lock a user into a choice they made at their first startup.
Version
0.12.9
Operating System
Linux
Distribution Method
deb (Linux)
Describe the issue
its really common that origin/master is the original repo, and myusername/whatever is "my fork", and contains "my branches", and that "origin" is almost-certainly the WRONG repo to interact with, and the only way to "switch", is to Project Menu->Project Settings->scroll to very bottom -> Remove Project an to "start over" completely and go back to the new-project wizard. GitKraken allows this trivially by right-clicking on a 'remote' and choosing Edit, or Adding a new Remote to the list of remotes, can't seem to see any way to do either of those in gitbutler. it feels unusable without these basic capabilities to me.
How to reproduce
use the default and recommended settings on a repo that has "upstream" ( non-writable remote ) configured as origin/master and use recommeneded defaults during repo-chooser / initial configuration page.
Expected behavior
make the implications of choosing the wrong/default remote smaller and easier to fix, and dont lock a user into a choice they made at their first startup.
Relevant log output
No response