On Mon, Dec 17, 2018 at 08:08:49AM -0500, Mark Kharitonov wrote: > C:\Dayforce\test [master ↓2 +0 ~2 -0 !]> git pull > error: Your local changes to the following files would be > overwritten by merge: > 2.txt > Please commit your changes or stash them before you merge. > Aborting > Updating 2dc8bd0..ea343f8 > C:\Dayforce\test [master ↓2 +0 ~2 -0 !]> > > Does git have a command that can tell me which uncommitted files cause > the this error? I can see them displayed by git pull, but I really do > not want to parse git pull output. That message is generated by merge-recursive, I believe after it's figured out which files would need to be touched. I don't offhand know of a way to get that _exact_ answer from another plumbing command. But in practice it would probably be reasonable to ask for the diff between your current branch and what you plan to merge, and cross-reference that with the list of files with local changes. Something like: git pull ;# this fails, but FETCH_HEAD is left over git diff-tree -z --name-only HEAD FETCH_HEAD >one git diff-index -z --name-only HEAD >two comm -z -12 one two would work on Linux, but "comm -z" is not portable (and I suspect you may not have comm at all on Windows). You can probably find a way to show the common elements of the two lists using the scripting language of your choice. The answer that gives will be overly broad (e.g., in a case where our local branch had touched file "foo" but other side had not, we'd consider "foo" as a difference the two-point diff-tree, whereas a real 3-way merge would realize that we'd keep our version of "foo"). But it might be good enough for your purposes. -Peff
