After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 702642 - Refresh is ambiguous
Refresh is ambiguous
Status: RESOLVED NOTABUG
Product: gitg
Classification: Applications
Component: gui
git master
Other Linux
: Normal normal
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2013-06-19 11:23 UTC by Allan Day
Modified: 2014-12-14 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allan Day 2013-06-19 11:23:16 UTC 
Does refresh mean "pull --rebase"? As a rule, it is good to have simple, familiar names for UI. At the same time, it is important to reflect the context of use. In this case, I would try to be roughly consistent with the git command line interface. Maybe "Pull" would be better.

Also, since pull is one of the most common (if not *the* most common) actions you will want to do, I'd maybe add a button for this to the toolbar.
Comment 1 Ignacio Casal Quinteiro (nacho) 2013-06-19 11:25:42 UTC 
Refresh, mainly reloads the commit list since it may have changed or something. I guess we could also do this from the focus event
Comment 2 Sindhu S 2013-06-20 04:42:03 UTC 
Can this bug be closed since it was filed about the term 'Refresh' not being understood in context of Gitg and now that, that is clear?
Comment 3 Allan Day 2013-06-20 10:47:14 UTC 
(In reply to comment #1)
> Refresh, mainly reloads the commit list since it may have changed or something.
> I guess we could also do this from the focus event

In that case I would expect the refresh button to be part of the commit header rather than being in the toolbar.

I would also possibly rename it to "Reload Commit" or something.
Comment 4 Ignacio Casal Quinteiro (nacho) 2013-06-20 10:52:06 UTC 
Allan, see that it does not reloads one commit, but the whole repository
Comment 5 jessevdk@gmail.com 2014-12-14 19:24:27 UTC 
I think refresh is pretty much what it does. It refreshes gitg with potentially changed state as on disk. Ideally this wouldn't happen, but it's easy to go to the command line and change something for which we can't get a notification.