We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discard changes fails due to index.lock already exists
Go to a directory that represents cloned git repository
Make changes to a given file
Click on the icon to pull from the repository
Now, try go discard the changes in order to be able to pull from the repository
Discard fails due to index.lock is already present
index.lock
Discard should discard the changes for the file
It seems that on the second try it actually behaves well, needs to investigate it further.
The text was updated successfully, but these errors were encountered:
This seems related to the following git config in my environment
[branch] autosetuprebase = always
Maybe we could check for this and decide if we should use git merge --abort versus git rebase --abort
git merge --abort
git rebase --abort
Sorry, something went wrong.
This should be fixed by #564
No branches or pull requests
Description
Discard changes fails due to index.lock already exists
Reproduce
Go to a directory that represents cloned git repository
Make changes to a given file
Click on the icon to pull from the repository
Now, try go discard the changes in order to be able to pull from the repository
Discard fails due to
index.lock
is already presentExpected behavior
Discard should discard the changes for the file
Context
Workaround
It seems that on the second try it actually behaves well, needs to investigate it further.
The text was updated successfully, but these errors were encountered: