As the other answers explain, you can use two commands: git submodule status, or git ls-tree HEAD, taking only the lines where the second column is commit (if you have awk you can use git ls-tree HEAD | awk ‘$2 == “commit”‘). However, these commands give different results! What’s the difference? git submodule status always … Read more
There is a web-based workaround: Create a temporary branch, switch to it; Edit multiple files, commit each file separately; Make pull request; Under Merge pull request button, choose Squash and merge (if the repo allows it), then confirm merge; Delete temporary branch. I use this method on a PC which I don’t want to install … Read more
try this command git log –format=”%H” -n 1
You’re meant to put the commit message in this text file, then save and quit. You can change the default text editor that git uses with this command: git config –global core.editor “nano” You have to change nano to whatever command would normally open your text editor.
I realize people can google and come here to find a simpler answer: What if it was just the last commit? (OP’s question is for fixing the 4th commit back in history) In the case you commit and realize you forgot to add some file immediately, just do: # edited file-that-i-remember.txt git add file-that-i-remember.txt git … Read more
Have you confirmed that code is accessible from the command line where you execute git commands? You could run code –version BTW. When I execute where code I get C:\Program Files\Microsoft VS Code\bin\code – it’s no longer installed in the %App_Data% folder. However, this should be irrelevant if you only specify code –wait without the … Read more
View => Tool Windows => Version Control. (Windows (Alt + 9) / OS X (Cmd + 9)) IntelliJ 2017.1 and higher => Go to Log and right click + reword or press F2. While you are on the same branch, ( your checked out branch is the same )
To get back to that commit you can use the reflog to look up it’s ref. Reference logs, or “reflogs”, record when the tips of branches and other references were updated in the local repository. Run this command: git reflog Scan the first few entries, and find the commit that was lost. Keep track of … Read more
For others having the same problem, try running git add . which will add all files of the current directory to track (including untracked) and then use git commit -a to commit all tracked files. As suggested by @Pacerier, one liner that does the same thing is git add -A
Git generally doesn’t throw anything away, but recovering from this may still be tricky. If you have the correct source then you could just push it into the remote with the –force option. Git won’t have deleted any branches unless you told it to. If you have actually lost commits then take a look at … Read more