Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 382274 - can't create a remote branch when pushing from new topic branch
Summary: can't create a remote branch when pushing from new topic branch
Status: CLOSED DUPLICATE of bug 360266
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.5   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-11 12:13 EDT by Susan McCourt CLA
Modified: 2012-06-11 13:51 EDT (History)
0 users

See Also:


Attachments
screenshot (82.92 KB, image/png)
2012-06-11 12:13 EDT, Susan McCourt CLA
no flags Details
screenshot - various scrollbar states (36.91 KB, image/png)
2012-06-11 13:49 EDT, Susan McCourt CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2012-06-11 12:13:19 EDT
Created attachment 217169 [details]
screenshot

i'm trying to push a fix to a remote topic branch for review for RC2.  However the branch prompter doesn't give me the option to create a new remote branch.  See screenshot....

Only a small subset of the branches on the remote are shown in the prompter, and the [New] entry is not shown.  If I "view all" branches from the respository page, I can see many more branches.
Comment 1 Susan McCourt CLA 2012-06-11 13:49:29 EDT
Created attachment 217174 [details]
screenshot - various scrollbar states

Gosia helped me to look at the server response and determine that the correct responses are coming back.  We could see the dijit creating the tree nodes, etc., so she realized it's a scrollbar issue.

Embarrassingly, when I scroll the outer horizontal scrollbar all the way to the right, a new vertical scrollbar appears, revealing all the items.  See screenshot for various scrollbar states.
Comment 2 Susan McCourt CLA 2012-06-11 13:51:13 EDT

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