Push branch with no upstream defaults to first remote and not to "origin"

[pmme]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Executing push on a local branch with no upstream defaults to first configured remote (actually a colleague's computer) and not to the remote specifically named "origin".
I believe defaulting to "origin" would be consistent with the behaviour of executing 'git push' without specifying the remote.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

1. Configure a repository with two remotes, "origin" and one that is alphabetically earlier than "origin", e.g. "aremote"
2. Create a new branch.
3. Open the GitExtensions Push dialog.
4. Observe that the combo-box for Remote defaults to the first alphabetically sorted remote and not "origin".

What is the expected behavior?
Remote will default to "origin".

Which versions of GitExtensions, GIT and Windows are affected by this issue? Did this work in previous versions of our tool?

• GitExtensions 2.50.00
• git version 2.12.2.windows.1
• Windows 7
  As I recall, GitExtensions 2.49.* defaulted to pushing to "origin" if the branch did not have a configured remote.