问题
I can't pop my stash because I merged a branch which apparently conflicts with my stash and now my stash is seemingly unable to be popped.
app.coffee: needs merge
unable to refresh index
Anyone know how to resolve this?
FIXED!
Turns out the actual issue was an unresolved merge conflict from the merge, NOT that the stash would cause a merge conflict.
Resolution: Commit the conflicted file.
回答1:
First, check git status.
As the OP mentions,
The actual issue was an unresolved merge conflict from the merge, NOT that the stash would cause a merge conflict.
That is where git status would mention that file as being "both modified"
Resolution: Commit the conflicted file.
You can find a similar situation 4 days ago at the time of writing this answer (March 13th, 2012) with this post: "‘Pull is not possible because you have unmerged files’":
julita@yulys:~/GNOME/baobab/help/C$ git stash pop
help/C/scan-remote.page: needs merge
unable to refresh index
What you did was to fix the merge conflict (editing the right file, and committing it):
See "How do I fix merge conflicts in Git?"
What the blog post's author did was:
julita@yulys:~/GNOME/baobab/help/C$ git reset --hard origin/mallard-documentation
HEAD is now at ff2e1e2 Add more steps for optional information for scanning.
I.e aborting the current merge completely, allowing the git stash pop to be applied.
See "Aborting a merge in Git".
Those are your two options.
回答2:
I was having this issue, then resolving the conflict and commiting, and doing git stash pop again was restoring the same stash again (causing the same conflict :-( ).
What I had to do is git stash drop to get rid of it.
回答3:
Its much simpler than the accepted answer. You need to:
Check
git statusand unmerged paths under it. Fix the conflicts. You can skip this step if you'd rather do it later.Add all these files under unmerged paths to index using
git add <filename>.Now do
git stash pop. If you get any conflicts these will again need to be resolved.
回答4:
If anyone is having this issue outside of a merge/conflict/action, then it could be the git lock file for your project causing the issue.
git reset
fatal: Unable to create '/PATH_TO_PROJECT/.git/index.lock': File exists.
rm -f /PATH_TO_PROJECT/.git/index.lock
git reset
git stash pop
回答5:
I have found that the best solution is to branch off your stash and do a resolution afterwards.
git stash branch <branch-name>
if you drop of clear your stash, you may lose your changes and you will have to recur to the reflog.
回答6:
Here's how I solved the issue:
- git status (see a mix of files from a previous stash, pull, stash pop, and continued work.)
- git stash (see the needs merge issue)
- git add . (add the files so my work locally resolves my own merged)
- git stash (no error)
- git pull (no error)
- git stash pop (no error and continue working)
回答7:
You need to add app.coffee to staging.
Do git add app.coffee and then you will be able to apply your stash (after that commit and push).
回答8:
The stash has already been applied to other files.
It is only app.coffee that you have to merge manually. Afterwards just run
git reset
to unstage the changes and keep on hacking.
来源:https://stackoverflow.com/questions/9739352/git-stash-pop-needs-merge-unable-to-refresh-index