Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330504 - Decorations for Committed but not Pushed
Summary: Decorations for Committed but not Pushed
Status: CLOSED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.3   Edit
Assignee: Robin Stocker CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-17 13:58 EST by Miles Parker CLA
Modified: 2013-03-18 07:32 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2010-11-17 13:58:30 EST
After committing changes to local git repos but not pushing them, there is no visual indicator that the changes have not been pushed. It would be nice to be able to optionally see changes that are not in sync with remote repos. I don't know if this is practical performance wise but perhaps it could occur at the commit stage. This is all related to making EGit more transparent and easier to use for people migrating from traditional VCS.
Comment 1 Mark Soderquist CLA 2012-01-10 15:27:15 EST
I'd like to add my support for this enhancement request. I can't tell you how many times I have gone home without pushing my completed work for the day. A visual indicator would be very helpful.
Comment 2 Dani Megert CLA 2012-01-11 03:56:01 EST
(In reply to comment #0)
> After committing changes to local git repos but not pushing them, there is no
> visual indicator that the changes have not been pushed. It would be nice to be
> able to optionally see changes that are not in sync with remote repos. I don't
> know if this is practical performance wise but perhaps it could occur at the
> commit stage. This is all related to making EGit more transparent and easier to
> use for people migrating from traditional VCS.

+1
Comment 3 Markus Keller CLA 2012-01-11 07:17:08 EST
The implementation can be as simple as checking whether current HEAD is the same as the remote branch tip.

If they differ, then show a decoration on the project and the repository.

In the History view, the same decoration could e.g. be shown instead of the 'o' in the diagram at the left for all commits that have a local branch tag (e.g. 'master') but the corresponding remote branch tag (e.g. origin/master) is on a parent of that commit.
Comment 4 Miles Parker CLA 2012-01-11 12:31:52 EST
(In reply to comment #3)
> The implementation can be as simple as checking whether current HEAD is the
> same as the remote branch tip.

Yep, that makes sense. Would that handle the case where the user is working against a remote (non-master) branch?
Comment 5 Robin Rosenberg CLA 2013-03-17 17:05:00 EDT
This has been fixed in 2.2. A decoration on the project shows arrows indicating the number of commits relative to the upstream branch.

https://git.eclipse.org/r/#/c/4678/
Comment 6 Robin Stocker CLA 2013-03-18 07:32:43 EDT
This was already available in 1.3:

http://wiki.eclipse.org/EGit/New_and_Noteworthy/1.3#Branch_Status_Decoration