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

Bug 339564

Summary:	[client] Git UI for managing branches, push and pull
Product:	[ECD] Orion	Reporter:	Szymon Brandys <Szymon.Brandys>
Component:	Client	Assignee:	Project Inbox <e4.orion-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, libingw, susan, tomasz.zarna
Version:	0.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Szymon Brandys

2011-03-10 12:58:58 EST

I think we can manage branches and do Git push/pull on the Git Repositories UI (see Bug 338226). I would be similar to EGit way then. Boris mentioned though that we should consider having a separate piece of UI for branches, pull/push etc.

Thoughts?

Comment 1 Susan McCourt

2011-03-10 13:15:10 EST

> Thoughts?

I think we should always start with its own page as a way to just make sure that the function is built with loose coupling.

But I think we are starting to get enough pages, some of them simple enough, that people are going to want to combine functionality.

I opened bug 339566 to start thinking about "show view."

Comment 2 Boris Bokowski

2011-03-10 13:37:21 EST

My thinking was that we need two pages, because there's a difference between operations on a single existing repository (git branch, git checkout, git push/pull) and operations that create new repositories (git init, git clone). The latter could live on a general Git page (one that we link to from the header?), the former would be parameterized with the repository it operated on.

Comment 3 Szymon Brandys

2011-03-30 10:29:00 EDT


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