Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369297 - new repo page - no way to get git log of a remote
Summary: new repo page - no way to get git log of a remote
Status: CLOSED DUPLICATE of bug 373144
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 369591
  Show dependency tree
 
Reported: 2012-01-20 16:43 EST by Susan McCourt CLA
Modified: 2012-06-14 04:05 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2012-01-20 16:43:29 EST 
I was trying to examine a contribution made via github.  I added the contributor's remote on the new repo page (great!) but I can't see the git log of it.  Had to go to the old page.

This is important for the "committing contributions" workflow
Comment 1 Susan McCourt CLA 2012-01-22 18:17:46 EST 
I did a fetch on the remote at the time, but since the list of branches didn't change, I thought that it just didn't work.  Szymon told me that you can click on the "see all branches" link to see all branches from all repos.  That wasn't too obvious to me in this workflow (I'm trained from the old tree page to look for change underneath the repo vs. above, plus nothing changed.)  Maybe just some kind of indicator near the "see all branches" link, could let me know that I something to make new branches available.  

I'm not suggesting a general mechanism for telling me there is new stuff on the server, just a way to help me so that if I caused a change in data from the page, it shows me where I need to go to see it.
Comment 2 Szymon Brandys CLA 2012-01-23 04:01:24 EST 
I'll suggest something here by 0.4.
Comment 3 Susan McCourt CLA 2012-06-13 15:03:35 EDT 
Actually at this point I think we can just consider this a dup of bug 373144.  The symptom was a little different, but the solution is the same.  If the remote tracking branch is visible on the repositories page by default, then it's easy to get to git log (this bug) and it's easy to do the fetch (bug 373144).

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