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

Bug 347095

Summary:	[client][log] navigating git log, scope of git log
Product:	[ECD] Orion	Reporter:	Susan McCourt <susan>
Component:	Git	Assignee:	Project Inbox <orion.git-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	simon_kaegi, Szymon.Brandys
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Susan McCourt

2011-05-24 20:19:19 EDT

this is a minor point...curious what others think.

Several times today I chose git remote with the intention to synch up with the latest.  But I'm often several levels deep in the navigator so I get the scoped history.  I'm always surprised when the log page comes up and I only see a couple of commits and then I realize the problem.

Some ideas:

- when a file is the selected item, could we name the commands "Local History" and "Remote History"?  At least I'd remember at the file level what I'm getting.
- I wonder if we should have a toolbar command that does git log at the repo level all the time.  Maybe we could put that in the command name.  Then I could always hit that one when my intention is to fully synch up, regardless of where I happen to be parkd in the navigator.

Comment 1 Susan McCourt

2011-05-25 11:26:42 EDT

maybe this was a performance related complaint.  Yesterday after working most of the day on orion.eclipse.org, it was very sluggish to navigate the git log page breadcrumb and reload the content to show the repo scope.

Today it is more responsive (restarted my browser).

So perhaps the practical suggestion in this bug is that we should use a label besides the breadcrumb to make it really clear what scope we are looking at.  The breadcrumb feature is way cool but for initial users we may want reinforcement.

Comment 2 Susan McCourt

2011-05-25 11:28:21 EDT

I suppose one could argue the breadcrumb is too small....

Comment 3 Susan McCourt

2011-05-25 12:06:14 EDT

Sorry for taking this bug all over the place.  
Retitling it since this is really a discussion of page scope and how to navigate it.

I opened bug 347181 to deal with the breadcrumb presentation and consistency issues.  I think you can assume we'll come up with a suggestion for the visibility problem in that bug.

Comment 4 Susan McCourt

2011-05-25 13:18:10 EDT

I think that once we can get to git log and push from the git-status page, this workflow won't bug me.  Right now I'm always going to git-status, committing, then I have to go find a navigator so I can go hover over anything, so I can get a git log command, so I can go to git log, so I can navigate back to the root.

Comment 5 Susan McCourt

2011-05-26 00:12:47 EDT

It is definitely confusing that "Push" only shows up when you are at the repository root.  I just stared at the git log page and reloaded it 3 times, went back to git remote, went back to git log, etc...looking for "Push."

Of course I didn't realize I wasn't at the root (I often work at the org.eclipse.orion.client.core level and to me that feels like the root).  Once I realized the issue, I guessed that I couldn't push while not in the root.

(yes, I think I argued once that pushing when not at the root could be dangerous, and I think we have another bug about this problem).

But again, the scoping really tripped me up while trying to get work done.
Mostly that I don't know where I am.

Even if we make the breadcrumb bigger or whatever.
If we are going to limit what the user can do, maybe we want some helpful links that say stuff like, "if you want to push, you must go the repository root" or whatever.

Comment 6 John Arthorne

2015-05-05 14:49:42 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html