git add . creates a index.lock file but then I cannot commit because of the index.lock file? #58922
Unanswered
kevinabbot
asked this question in
New to GitHub
Replies: 1 comment 1 reply
-
|
Do you have any other program running that might look at the repository, e.g. an IDE with Git integration? It's possible it notices the changed index and then goes to update its own state from there, or similar things. 🤔 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am really confused as to why I cannot make a commit. Here is my command line workflow:
git add . git commit -m "pleasework2" git pushWhen I do git add . it creates the index.lock file but then when I try to commit it says I can't because of another process running.
All of this is being done on one terminal..
Update: While watching it play out in the file folder it removed it self after doing git add . but earlier it would be done but the file would stay not letting me commit.. Do I need to give it a second to recognize that git add . is done before doing git commit? I only ask because this is all run in a batch file so it goes fast as possible.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions