Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360540

Summary: [client] Confusing workflow when pushing new branch
Product: [ECD] Orion Reporter: Mark Macdonald <mamacdon>
Component: GitAssignee: Project Inbox <orion.git-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 0.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Mark Macdonald CLA 2011-10-11 09:40:44 EDT 
Orion 0.3RC1 (0.2.0.v20111007-2111)

1. Create a new local branch.
2. Commit something on the branch.
3. Go to git-log, click "Push All".
4. The Choose Branch dialog appears. It lists existing remote branches. But there is no way to provide the name of a new remote branch to push to.
Comment 1 John Arthorne CLA 2011-10-11 14:06:42 EDT 
It automatically creates a remote branch with the same name when I try this. Is the issue that you want to use a different name for the remote branch?
Comment 2 Mark Macdonald CLA 2011-10-11 14:26:42 EDT 
(In reply to comment #1)
> It automatically creates a remote branch with the same name when I try this. Is
> the issue that you want to use a different name for the remote branch?

Oops, I didn't realize that the new remote branch appears in the "Choose Branch" list. Forcing local and remote branches to have the same name is fine with me.
Comment 3 John Arthorne CLA 2011-10-12 16:32:41 EDT 
I had the same confusion the other day, which is how I came to know that the branch is shown. If you are pushing to a remote that already has many branches, it's confusing and you might not notice that it has added that extra branch name to the list. Maybe a simple improvement would be to select that branch by default so in the 99% case you can just hit Enter or click Ok when prompted for a branch.
Comment 4 Tomasz Zarna CLA 2011-10-14 07:36:16 EDT 
Mark, do you think we can mark this one as a dupe of bug 355108?
Comment 5 Mark Macdonald CLA 2011-10-14 09:28:54 EDT 
Yup

*** This bug has been marked as a duplicate of bug 355108 ***