Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339564 - [client] Git UI for managing branches, push and pull
Summary: [client] Git UI for managing branches, push and pull
Status: CLOSED DUPLICATE of bug 339722
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 12:58 EST by Szymon Brandys CLA
Modified: 2011-08-30 10:21 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Brandys CLA 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 CLA 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 CLA 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 CLA 2011-03-30 10:29:00 EDT

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