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

Bug 326304

Summary: untracked file label decoration is not propagated to ancestors
Product: [Technology] EGit Reporter: Rizsike <asch>
Component: UIAssignee: Project Inbox <egit.ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: daniel_megert, markus.kell.r, matthias.sohn, patrick, stefan.lay
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Screenshot where a decorator should be seen on the project none

Description Rizsike CLA 2010-09-27 09:51:30 EDT 
Build Identifier: 20100617-1415

Untracked files labels are decorated with a question mark. Folders and projects containing untracked files are not decorated though.

Other changes in the working copy are shown on the ancestor correctly.


Reproducible: Always

Steps to Reproduce:
1. Add a new local git repository
2. Import a project from the reporsitory into Workspace
3. Create a new file in the project
Comment 1 Rizsike CLA 2010-09-27 09:53:15 EDT 
Created attachment 179638 [details]
Screenshot where a decorator should be seen on the project
Comment 2 Stefan Lay CLA 2010-10-22 07:50:22 EDT 
This is the intended behavior. If you want to find untracked files you can open the commit dialog.
Comment 3 Patrick Holthuizen CLA 2010-10-24 14:52:23 EDT 
Why is this intended behavior? I think this behavior enlarges the chance on errors. If I have several related projects open at the same time and I only added some resources to one project which become untracked. Then there is a chance I can forget to commit those changes if they are not visible on the project top level node. How should egit work in such a case?
Comment 4 Stefan Lay CLA 2010-10-25 04:55:06 EDT 
I think the propagation was not done due to performance reasons. But I see your point. Other team providers like cvs or mercurial have a preference "Compute deep decoration state". 

I'll reopen this bug as an enhancement request.
Comment 5 Dani Megert CLA 2012-01-05 11:19:38 EST 
This is really a bug because one might miss to commit & push a new file.
Comment 6 Dani Megert CLA 2012-01-05 11:22:33 EST 

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