Eclipse Community Forums: EGit / JGit » Eclipse pull is causing dirty

Home » Eclipse Projects » EGit / JGit » Eclipse pull is causing dirty_worktree error(git pull is causing dirty_worktree)

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse pull is causing dirty_worktree error [message #1508833]

Fri, 12 December 2014 19:13

srijava srijavakanth

Messages: 4
Registered: December 2014

Junior Member

Hi all,

Please help me to understand the dirty_worktree issue.

some of the member in team getting this error not everyone.

Trying to download the code (Fetch from remote and Pull)

While doing the pull, it shows the name of the file and says dirty_worktree.

Please help me to understand this issue and how I can solve this.

Thank You,

Report message to a moderator

Re: Eclipse pull is causing dirty_worktree error [message #1565668 is a reply to message #1508833]

Thu, 15 January 2015 12:10

Matthias Sohn

Messages: 1268
Registered: July 2009

Senior Member

JGit/EGit here prevent that you overwrite modifications you did locally in your working tree.
So if e.g. file A is locally modified and these modifications aren't yet committed and you try
to pull new commits from the server which also modify file A then JGit aborts the pull operation
to prevent that the version of file A coming from the server overwrites your local changes in
the same file.

Report message to a moderator

Re: Eclipse pull is causing dirty_worktree error [message #1773616 is a reply to message #1565668]

Sat, 30 September 2017 14:56

Sara Caruso

Messages: 1
Registered: September 2017

Junior Member

Hi,
I have the same situation: Pull fails because I have some local changes. What can I do to solve this problem? It's enough do right click on the project, then Team, then Commit....
After that can I make Team, then Pull?

Report message to a moderator

Re: Eclipse pull is causing dirty_worktree error [message #1773691 is a reply to message #1773616]

Tue, 03 October 2017 04:53

Ed Merks

Messages: 33142
Registered: July 2009

Senior Member

I always hate it when that happens. One approach is to copy the particular files that are blocking the pull to somewhere else (or to a renamed form next to the old one) and then comparing what's pulled with what you have before to merge them. Another approach is to use Team -> Stashes -> Stash Changes... and "commit" the dirty files to the stash; I'm always a little scared to do that because I'm sure applying the stash will have merge problems too, and then I'm not completely sure I'll be able to easily recover what's in the stash.... But I think that's the proper approach to take...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Eclipse pull is causing dirty_worktree error [message #1774525 is a reply to message #1773691]

Mon, 16 October 2017 19:26

Matthias Sohn

Messages: 1268
Registered: July 2009

Senior Member

It depends on what you want to achieve.
If you don't need the local changes you can reset hard to get rid of them.
Otherwise either commit or stash them. Then you can later go back to this change and continue working on it.

Report message to a moderator

Previous Topic:	Non-fast-forward reject caused loss
Next Topic:	Finding a repository

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 07:32:17 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter