> Hmm. What happens with `git push` from console? (see tab button beside >> [commit, diff, file tree, ...] in Git Extensions, or just from a regular >> command prompt). Any error messages? >> > > That pushes to my fork, but not upstream to Leo. It works fine. Do you > think it's worth cloning Leo using Git-Ext? Right now, I have the fork, > managed with Git Ext, and the Leo clone, managed by Github Desktop. >
Ahh, I think I see now. You need to add a new remote to push to. This could be done in any client, but I only know how for git extensions. Once the remote(s) are set all the clients should be able to use them. Right now in the GitExt manged repo the remote named "origin" is probably set to your personal fork. Right click on "Remotes" >> select "Manage" >> then [+] to add a new remote. Call it 'upstream' (or anything else that makes sense to you) and put in Leo's repo address for url: https://github.com/leo-editor/leo-editor.git When you save changes the next prompt is confusingly worded. What it's really asking is: *"make this new remote the default one?"*. >From this point on, when you use the Push or Pull dialogs (via dropdown) you can choose between Origin (yours) and Upstream (Leo Editor organization) for the destination. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b8cd5f2e-84af-47f3-9369-8766fbdf2881%40googlegroups.com.
